-
-
Notifications
You must be signed in to change notification settings - Fork 355
feat: support custom platform version #170
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
feat: support custom platform version #170
Conversation
91df9ba
to
ae820e2
Compare
ae820e2
to
6aeebf6
Compare
6aeebf6
to
1756d3f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is needed. 👍🏻
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@antonbabenko verified this change - good to merge 👍🏼
@jychen7 it would be good if you could update the |
@bryantbiggs sure, done in 5826a01 |
thank you @jychen7 - @antonbabenko good to go 👍🏼 |
Great! v2.29.0 has been just released. |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
Allow to set custom ECS Fargate platform version
Motivation and Context
currently, by default, ECS Fargate is using platform version 1.3.0
However, 1.4.0 introduce more features I would like Atlantis to use, including
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-task-storage.html
Breaking Changes
Nope, new variables are backward compatible and match existing defaults
How Has This Been Tested?
planed and applied