fix: increase cloudformation stack timeout #23
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.
Summary
Fix error when using the module to deploy cloudformation stacks in multiple AWS accounts
The default timeout to deploy cloudformation stack is 30 minutes, in my environment this is enough time to deploy to approximately 30 AWS accounts, the problem is that my organization has more than 30 AWS accounts
Issue
Error example:
Reference documentation:
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudformation_stack_set_instance#timeouts
https://developer.hashicorp.com/terraform/language/resources/syntax#operation-timeouts