-
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
aws_ecs: ec2Service placement strategies use incorrect casing which causes drift #20812
Labels
@aws-cdk/aws-ecs
Related to Amazon Elastic Container
bug
This issue is a bug.
effort/small
Small work item – less than a day of effort
p1
Comments
4 tasks
Thanks for reporting this @tea-418, someone should be able to look at the PR soon |
mergify bot
pushed a commit
that referenced
this issue
Jul 30, 2022
…causes drift (#20946) Fixes #20812 Switches lowercase cpu and memory placement strategy to uppercase as required by cloudformation: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-placementstrategy.html ---- ### All Submissions: * [x] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
josephedward
pushed a commit
to josephedward/aws-cdk
that referenced
this issue
Aug 30, 2022
…causes drift (aws#20946) Fixes aws#20812 Switches lowercase cpu and memory placement strategy to uppercase as required by cloudformation: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-placementstrategy.html ---- ### All Submissions: * [x] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/aws-ecs
Related to Amazon Elastic Container
bug
This issue is a bug.
effort/small
Small work item – less than a day of effort
p1
Describe the bug
When adding the packedByCpu() PlacementStrategy to a new ecs service, the cf template generated has the Property
However this will cause the Stack to drift as CF only allows CPU spelled in uppercase.
See here: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-placementstrategy.html
Expected Behavior
CDK should generate the "Field" attribute of "PlacementStrategies" according to CF demands.
In the CF Template PlacementStrategies should look like this:
Current Behavior
CDK generates the "Field" attribute of "PlacementStrategies" NOT according to CF demands but instead spells it in lowercase.
In the CF Template PlacementStrategies actually looks like this:
Reproduction Steps
Generate a fresh cdk project with
cdk init app --language=typescript -j
in the lib/project-name-stack.ts add a ecs service to a cluster with the PlacementStrategy set:
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.28.1 (build d035432)
Framework Version
No response
Node.js Version
v16.14.2
OS
Windows 10 Enterprise 21H2
Language
Typescript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: