aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
Support advanced concurrency behaviour
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
- not following the temple because this is more general than a specific service.
- first raised in https://github.com/aws-cloudformation/aws-cloudformation-resource-schema/issues/79#issuecomment-641909406
---
Some resources do not support having more than X concurrent changes. It would be nice if CloudFormation could be aware of those (they're usually already in the CloudFormation documentation as a comment), and never execute more than X actions on those types at the same time.
Preferably this is something that is tracked on the account/region level, but as a first step tracking it on the stack level would already be an improvement (and the api changes for the provider side would be the same for both).
Examples:
- AWS::DynamoDB::Table
Contributor guide
Assessment
This issue has not been assessed yet.