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

add platformVersion option #344

Merged

Conversation

bayashiok
Copy link

I received the following email from AWS

Starting March 8, 2021, AWS Fargate is changing the platform version (PV) LATEST flag to resolve to PV 1.4.0 instead of PV 1.3.0 [1]. PV 1.4.0 was launched in April 2020 and introduces a number of new features and changes [2].
[1] https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html
[2] https://aws.amazon.com/jp/blogs/news/aws-fargate-launches-platform-version-1-4/

Therefore, I changed the option of ecs-task so that I can specify the platform version.

@bayashiok bayashiok force-pushed the add-platformVersion-option-fargate branch 2 times, most recently from 5e7fa62 to 98d9363 Compare March 3, 2021 01:30
@bayashiok bayashiok force-pushed the add-platformVersion-option-fargate branch from 98d9363 to d12cad7 Compare March 3, 2021 01:33
@h3poteto h3poteto self-requested a review March 3, 2021 11:34
@h3poteto
Copy link
Owner

h3poteto commented Mar 3, 2021

I don't know your use case, but is there a case where you want to run fargate task with old PV?
And is there any problem when you run the old job on the new PV?

@bayashiok
Copy link
Author

I don’t want to run a Fargate task on an old PV.
Since the LATEST changes with AWS timing, I may want to change the PV and check the operation beforehand.
I want to control when to change the PV.

@h3poteto
Copy link
Owner

h3poteto commented Mar 5, 2021

I see.

@h3poteto h3poteto merged commit f66d2c5 into h3poteto:master Mar 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants