mirror of
https://github.com/dehydrated-io/dehydrated.git
synced 2026-01-11 22:30:44 +01:00
Feature request - allow update of email address #177
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nneul on GitHub (Dec 30, 2016).
According to
https://github.com/certbot/certbot/issues/1215
The API to do this already exists on the boulder side, POSTing a registration object with a changed contacts field to /acme/reg should update the registration.
It would be nice if there were an option to do this in dehydrated client. Or even better - do it automatically if the address in the config doesn't match the address in registration_info.json
@txr13 commented on GitHub (Dec 30, 2016):
It would be very helpful to have a way to update contact info from dehydrated.
I'm not as sure about updating it automatically when a change is made to the config, though... Given that the client can support multiple config files and multiple ACME servers, I think I would personally prefer that the contact update operation only be issued through manual invocation, rather than having something put through automatically.
@nneul commented on GitHub (Dec 30, 2016):
Perhaps a "Your contact information in configuration doesn't match registration, exiting..." error (or warning), combined with a "--update-registration" option that would cause it to react to that situation by updating the registration if needed.
@txr13 commented on GitHub (Dec 30, 2016):
I like the thought of a notification being dropped into the logs, possibly notated as a warning. Shouldn't cause the client to exit or abort the current execution.
--update-registration (or whatever the option is) should be able to be executed on its own. That is, without an accompanying -c or -d options.
In my own environment (for example), dehydrated is running under cron. I don't want changed contact info to abort a scheduled run... but if a notification / warning popped up in my cron logs, I'd be happy to log in and manually do an --update-registration to address that.
@lukas2511 commented on GitHub (Jan 9, 2017):
Duplicate of #239, closing this.