Open gjrtimmer opened 1 year ago
Hi,
I get your point; it makes sense. I just don't want to change the behavior for all users, but rather offer it as a configurable option. Because I'm not sure that it will suit everybody to stack backup files over and over.
How do you want to handle the retention strategy of these files? Just manually deleting old files?
I can offer an option like WUD_TRIGGER_DOCKERCOMPOSE_{trigger_name}_BACKUP_FILE_SUFFIX
The default value would be
back
to keep it backward compatible
And other possible values could be for example
${year}${month}${day}-${hour}${minute}${second}
where supported placeholders would be:
Would that resolve your issue?
I would like to request the rename of the backup extension.
I'm using docker-compose, and I have multiple services, because not every service receives an update at the same time I would like to suggest renaming the back extension.
I have mounted the folder of the docker-compose.yml so my backup file is written to the host. However, the backup file gets overwritten.
Proposal
Change the backup extension to
{DT}
DateTime Format
Format:
%Y%m%d-%H%M
Example: 20230221-2347Result
Backup filename:
docker-compose.yml.20230221-2347
This will keep all the different backups independent instead of overwriting each other, and also will tell you automatically when the file was updated.
I hope this request gets some consideration.