Open maxmuffin opened 3 months ago
Voting for Prioritization
Volunteering to Work on This Issue
Hi @maxmuffin did you use any workaround for now? Something like making terraform wait for a specific timeout after it initiated the mwaa creation?
Thanks
[!WARNING] This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.
Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.
Hi @preetsindhal , for now the resource has been created manually from the AWS console and imported directly into the terraform state to manage at least the update and delete operations.
Terraform Core Version
1.5.0
AWS Provider Version
5.39.0
Affected Resource(s)
aws_mwaa_environment
Expected Behavior
resource creation without errors
Actual Behavior
resource creation with error: waiting for MWAA Environment (airflow-environment) create: unexpected state 'PENDING', wanted target 'AVAILABLE', last error: %!s()
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
add attribute endpoint_management = "CUSTOMER" in aws_mwaa_environment resource
Debug Output
No response
Panic Output
No response
Important Factoids
MWAA required VPC endpoints needs to be managed by CUSTOMER. Selecting attribute endpoint_management equal to CUSTOMER, mwaa enter in PENDING state during creation, that is not supported.
References
No response
Would you like to implement a fix?
No