Use managed-execution in all stacksets #65
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Creating a
aws_cloudformation_stack_set_instance
that deploys to multiple regions in paralell is not yet possible due to hashicorp/terraform-provider-aws#24752, however using themanaged-execution
flag on theaws_cloudformation_stack_set
resources allows multipleaws_cloudformation_stack_set_instance
resources to be created in parallel. This has a similar effect, although more objects must be created, potentially neccesitating a higher-parallelism
flag onterraform apply
.This PR enables
managed-execution
for all stacksets created.Manual testing for a 4 account org, 5 regions, CSPM + EventBridge:
TF parallelism=10, managed-execution=false
TF parallelism=10, managed-execution=true
TF parallelism=100, managed-execution=true