Flexible backup path

What problem will this feature address?

Currently backup prefix is a fixed string. Can not backup to a path like backups/2024/09/01/xyz.tar.gz

Describe the solution you'd like

• Ability to define backup path including filename
• Ability to use date in backup path.

Describe alternatives you've considered

Default variable can be provided which will make this flexible. Variable can be identified by { } or [ ]. For example {month} or [month]

Path example:

• backups/{year}/{month}/{project}/{service}_{date}.tar.gz

Useful variables:

• project
• service
• container_name
• date
• month_digit
• month_name
• year_2_digit
• year_4_digit
• day_digit
• day_name
• date

Alternatively date related variables can be parsed and accept date formatting string for libraries like date-fns. That way we can just have {date:yyyy} or {date:MM}

Additional context

No response

No implementation files or tests are named. Start by locating the backup-prefix configuration and the code that generates backup paths, then define how the requested project, service, and date variables should expand. Done means configurable paths can include filenames and date-based directories, with coverage for the supported placeholders.