Frederik Ring

> I can try to provoke a failed copyBackup operation The easiest way I can think of would be to point the setup towards an inexistent bucket.

Thank you for this proposal. I've got a few questions for my understanding about how such a thing could look like: - where would such a setup persist its configuration?...

Although I do like the idea, I am not sure if having to add persistence isn't adding too much complexity for a rather simple tool like this. I'll leave the...

I have to admit I don't know anything about Kubernetes, so I might not be a good reference here. My gut feeling tells me this image probably won't work well...

This is an interesting proposal, however I am not sure if it's possible to do this in a configuration friendly way because of the following: right now, a `docker-volume-backup` container...

I think I prefer the second approach in the variation you describe. It's just very easy to understand and would cover a lot of cases. The option could be called...

Option 1 sounds enticing, but to be honest I'm not entirely sure how such a regexp that is derived from `BACKUP_FILENAME` could work in a way that it's guaranteed to...

> I'll propose, however, a little twist: what if we make a BACKUP_SELECTION_REGEX instead? This would allow for greater flexibility while still maintaining predictability. This is a brilliant idea considering...

@MMauro94 Just to coordinate with you: I am planning to move things around in here a bit in the next few days so a. we can have an easier way...

@MMauro94 I merged #100 so you can now a. decode Regular Expressions from configuration and b. access the list of files to be backed up outside of the archive mechanism...