-
Notifications
You must be signed in to change notification settings - Fork 4k
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
ecs: support new versionConsistency
on container definitions
#32202
Comments
This is in the L1 types in main as of #32175. |
One more complicated thing to consider might be disabling this feature by default for all containers that use a DockerImageAsset, though I don't know that that's possible even if it were agreeable. I think the semantics around DockerImageAsset tags are not in line with the problems this feature was designed to address, and the feature can thus produce needless latency added to ECS deployments of services that include DockerImageAsset containers. |
@isker , thanks for sharing the linked articles and information. I see that Cloudformation supports this and by default it's enabled -#32175. It might be a cause of concern to disable it , so it might require inputs from the Core team on how to proceed for PR contribution or if the team is already planning to get this available . Marking it as P2 as it might be helpful to have but would need team's input on how should this be proceeded with these scenarios in mind. Requesting team to share their insights on this request as how this can be implemented |
### Issue # (if applicable) Closes #32202. ### Reason for this change Support the new ECS::TaskDefinition ContainerDefinition VersionConsistency property. This is a simple enabled/disabled flag. ### Description of changes Add a simple enabled/disabled enum prop to the construct. More consequentially, default the prop to disabled (instead of unset) if the container image is a CDK asset, for the reasons described in the comments. ### Description of how you validated changes Unit and integration tests. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Comments on closed issues and PRs are hard for our team to see. |
Describe the feature
This new property is not present in the L2 constructs currently: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-taskdefinition-containerdefinition.html#cfn-ecs-taskdefinition-containerdefinition-versionconsistency
More details: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-ecs.html#deployment-container-image-stability
Use Case
Need to turn the "version consistency" feature off on my ECS service deployments.
Proposed Solution
No response
Other Information
Refer to aws/containers-roadmap#2394 for myriad users' struggles since this feature was added to ECS a few months ago.
Acknowledgements
CDK version used
2.167.2
Environment details (OS name and version, etc.)
N/A
The text was updated successfully, but these errors were encountered: