Closed suzuki-shunsuke closed 3 years ago
The simple solution is to remove waiting for the completion in the create function.
If you will create the new Deployment before the latest Deployment has been completed,
it would fail to create the new Deployment due to ConflictException
, but I think it is better to return the error immediately than to wait for the completion.
Due to the waiter,
terraform apply
isn't completed until the Deployment is completed.
It isn't desirable for some reasons.
deployment_duration_in_minutes
, this issue's problem would occurThis functionality has been released in v3.55.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.
For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!
I'm going to lock this issue because it has been closed for 30 days β³. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
Terraform CLI and Terraform AWS Provider Version
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
It is important that
aws_appconfig_deployment_strategy
'sdeployment_duration_in_minutes
is over20
.Debug Output
Panic Output
Expected Behavior
It succeeds to run
terraform apply
.Actual Behavior
It failed to run
terraform apply
due to the timeout.Steps to Reproduce
terraform apply
Important Factoids
References
DeploymentCreatedTimeout
is hardcoded to 20 minutes.So when it takes over 20 minutes to complete the deployment, it fails to create the Deployment.