-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
[Bug]: CloudFormation Stack instances are being executed sequentially when using region_concurrency_type = "PARALLEL" #30806
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
I can confirm this is indeed the case with 4.65.0, although I am not convinced this is related to the AWS provider or Terraform itself. I can see the settings in the Terraform plan and turning on the debug log, I can see the settings are sent with the API request. I have the same experience with My snippet: resource "aws_cloudformation_stack_set" "resource_explorer" {
name = "xzy"
permission_model = "SERVICE_MANAGED"
call_as = "DELEGATED_ADMIN"
auto_deployment {
enabled = true
retain_stacks_on_account_removal = false
}
template_body = file("${path.module}/template.yaml")
operation_preferences {
failure_tolerance_percentage = 99
max_concurrent_percentage = 50
region_concurrency_type = "PARALLEL"
}
} |
I did a lot of testing. I posted my findings here: #33170 (comment) |
Terraform Core Version
1.3.4
AWS Provider Version
4.60.0
Affected Resource(s)
aws_cloudformation_stack_set
aws_cloudformation_stack_set_instance
Expected Behavior
In AWS console CloudFormation Stack instances are being executed in parallel
Actual Behavior
In AWS console CloudFormation Stack instances are being executed sequentially
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Following code i being applied:
Steps to Reproduce
terraform apply
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: