AWS App Runner versioned images

KostLinux commented 4 months ago

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request Whenever you push a newer image to ECR (not overwriting the existing one, literally creating new image) - it should start auto-deploy for the serivce. So imagine a basic development having semantic versioned containers like: v1.0.1, v1.0.0 or 1.0.0 or 2024-02-19.1, so whenever you push a newer image to ECR like v1.0.2, it should automatically deploy it.

Describe alternatives you've considered None

Additional context We've talked with Saurabh from AWS Technical Support. He promised to deliver the feature request to you.

Attachments If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

freddy-mesa commented 4 months ago

Hi, did you try adding the latest tag to the ECR image, If you change the config to pull the latest tag of your image from ECR, App Runner will always automatically redeploy with the latest image tag.

KostLinux commented 3 months ago

Right now we're using the latest tag, but we want to use version tag instead.

jwerre commented 3 months ago

Duplicate issue: https://github.com/aws/apprunner-roadmap/issues/218

aws / apprunner-roadmap

AWS App Runner versioned images #236