I was testing a new PR which adds the option “force-actual-date” which is not for backups but for the Duplicati application.
I then changed to another code branch which did not have that option and now I keep get a warning that “force-actual-date” is not a valid option. However, since it is not in the code it isn’t displayed on the page and I can’t remove it.
This raises the question about removing options from Duplicati in the future. Going into the DB to remove it isn’t a good solutions for users when Duplicati happens to remove options in the future.
So how best to handle this? If an option is not available in the Duplicati application code should the option be to quietly remove it from the database? what about options for backups should the same happen?
I’m thinking unknown options should always be quietly removed from the DB and logged as informational. If not removed then there is a chance a future option with maybe a different function but with the same name could have very unexpected results for a user.