Fix: Update LATEST_VERSION_ID env variable in Buildspec and Image tag in ECS Task definition #7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ect and image tag (if user does not provide a desired image tag) in the ECS Task definition to fix issue with S3 object version IDs that can start with a "." which is not a valid docker image tag.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the app assets are uploaded as a ZIP file to the S3 bucket, there is an edge case where the S3 object version ID potentially starts with a period ("."). If an attempt is made to use the same version ID as an image tag during Docker Image build, the Build fails. This fix prepends the S3 object version ID with a character "v" as the Image tag in the Codebuild Buildspec configuration and the ECS Task definition.
Attached files demonstrate the issue: