-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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(ecs): secret JSON field for Fargate tasks #11348
Conversation
Fargate tasks running on platform version 1.4 can now reference a specific JSON field of a secret stored in Secrets Manager. Remove the error `ContainerDefinition` and add a check on the platform version in `FargateService`. See https://aws.amazon.com/about-aws/whats-new/2020/11/aws-fargate-for-amazon-ecs-launches-features-focused-on-configuration-and-metrics/ Closes aws#11341
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.
One small nit, but otherwise LGTM! Thanks for the speedy turnaround!
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.
🎉 Thanks @jogold !!
Pull request has been modified.
@SoManyHs Can you reapprove? You merged from master after reviewing, this dismisses the review. |
@SoManyHs ping |
@SoManyHs an approval would be much appreciated, so we can use the feature within our deployments :-) |
@marcotesch you can use the following workaround in the meantime #11341 (comment) |
Ah, didn't see that. Sorry about the delay! |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Fargate tasks running on platform version 1.4 can now reference a
specific JSON field of a secret stored in Secrets Manager.
Remove the error in
ContainerDefinition
and add a check on theplatform version in
FargateService
.See https://aws.amazon.com/about-aws/whats-new/2020/11/aws-fargate-for-amazon-ecs-launches-features-focused-on-configuration-and-metrics/
See aws/containers-roadmap#385 (comment)
Closes #11341
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license