Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve date in AWS_S3_PATH #397

Closed
Simusharp opened this issue Mar 22, 2024 · 1 comment
Closed

Resolve date in AWS_S3_PATH #397

Simusharp opened this issue Mar 22, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@Simusharp
Copy link

Is your feature request related to a problem? Please describe.
When backing up, I prefer to create a S3 path with a time stamp. Unfortunately, using %Y in path variable doesn't resolve.

Describe the solution you'd like
I would like to set path as follows: AWS_S3_PATH="backup-%Y-%m-%d" and have it resolve to backup-2024-03-21.

Describe alternatives you've considered
N/A

Additional context
N/A

@m90
Copy link
Member

m90 commented Mar 22, 2024

Implementing this would be a breaking change, and putting it behind a flag seems too specific for me right now.

I am aware that variable expansion / templating in configuration values currently is way too piece-meal, but there's no easy way out unless the changes made are breaking. I do consider unifying this in a v3 in any case: #80

In case you really need the date in the directory instead of the filename, you could use the following workaround:

  • Create a Docker image based off this one and install either the AWS CLI or the MinIO client
  • In a labeled copy-post command on the backup container itself, mv the file that has been created to the desired location

@m90 m90 closed this as not planned Won't fix, can't repro, duplicate, stale Mar 22, 2024
@m90 m90 added the enhancement New feature or request label Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants