I'd like an option to not generate backups when running dehydrated --account, because currently the backups just don't get automatically cleaned up otherwise. And I really have no use for these backups.
Why not just delete the backup files if I don't need them?
Well not only is that inconvenient, but in my case, I'm developing a Docker image integrating dehydrated with a declarative config. Ideally, a user of my image should be able to change their ACME account email without having to manually go into the Docker volume to delete these backup files. I could delete them automatically, but dehydrated also outputs a message saying the file was backed up, so deleting them would make that message misleading.
Suggestion
I'd like an option to not generate backups when running
dehydrated --account, because currently the backups just don't get automatically cleaned up otherwise. And I really have no use for these backups.Here's the line that backs up the file:
https://github.com/dehydrated-io/dehydrated/blob/4fd777e87e589652b1127b79ac6688ed7cb151fe/dehydrated#L1657
Why not just delete the backup files if I don't need them?
Well not only is that inconvenient, but in my case, I'm developing a Docker image integrating
dehydratedwith a declarative config. Ideally, a user of my image should be able to change their ACME account email without having to manually go into the Docker volume to delete these backup files. I could delete them automatically, butdehydratedalso outputs a message saying the file was backed up, so deleting them would make that message misleading.