greenlock.manager.remove({subject}) doesn't work #56
Notiek ielāde…
x
Atsaukties uz šo jaunā problēmā
Block a user
Nav sniegts apraksts.
Dzēst atzaru "%!s()"
Atzara dzēšana ir neatgriezeniska. Kaut arī izdzēstais zars neilgu laiku var turpināt pastāvēt, pirms tas tiešām tiek noņemts, to vairumā gadījumu NEVAR atsaukt. Vai turpināt?
greenlock.manager.remove({subject}) doesn't work, it never finds a site by
subject`.npx greenlock remove --subject
has the same problem.I've tried debugging and this is what I came up with:
In
https://git.coolaj86.com/coolaj86/greenlock.js/src/branch/master/lib/manager-wrapper.js#L203
the public manager api is exposed. The remove function expects {subject}, it checks and refuses to take
servername
oraltname
.The remove function in the wrapper calls the merged
remove
function, which callsmega.get
:https://git.coolaj86.com/coolaj86/greenlock.js/src/branch/master/lib/manager-wrapper.js#L475
The opts to
mega.remove
at this time are{subject}
.mega.get
however, uses{servername, wildname}
.A workaround is to use
greenlock.manager.set({subject, deletedAt: Date.now()})