-
Notifications
You must be signed in to change notification settings - Fork 0
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
Travis CD to AWS S3 - Versioning and Old File Cleanup #22
Comments
Placing releases to the versioned folders (i.e. cedict-1.0.1, cedict-1.0.2, etc.) would make this simpler, I think. We can then have a script that will scan folders and read a version. Based on that it can decide whether a folder be removed or not. We can use Amazon API Gateway to hide those versioned folders from the outside world. Here is what Even Financing is using:
The piece above is taken from Continuous Release Pipeline with Travis CI. @balmas, what do you think? |
In general, I am okay with using versioned folders, but I would like to avoid introducing another AWS dependency if we can help it (as we pay for API gateway usage) Since the buckets are already served by a cloudfront distribution, perhaps we could figure out how to handle pointing at the right versioned folder via the cloudfront configuration? |
here's the cloudfront terraform file |
Thanks, I will check it out |
Currently, Travis CD configuration does not provide any way to remove obsolete files from an AWS S3 bucket. From the Travis S3 docs:
Because of this we have to establish a process that will clean older files from the S3 bucket on its own, not relying on Travis CD.
The text was updated successfully, but these errors were encountered: