Closed pguinard-public-com closed 1 year ago
Voting for Prioritization
Volunteering to Work on This Issue
Related #28913 Related: #29022
Hey @pguinard-public-com 👋 Thank you for taking the time to raise this! A fix for this has just been merged, and will go out with the release later this week. Given that, I'll go ahead and close this issue. If you think I've done this in error, please do let me know.
Hey @pguinard-public-com 👋 Thank you for taking the time to raise this! A fix for this has just been merged, and will go out with the release later this week. Given that, I'll go ahead and close this issue. If you think I've done this in error, please do let me know.
This is what I get for searching open issues! 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.
Terraform Core Version
1.3.7
AWS Provider Version
4.51.0
Affected Resource(s)
Expected Behavior
cidr, ipam_pool_allocation_id,
terraform console Acquiring state lock. This may take a few moments...
Actual Behavior
Actual behavior (sometimes):
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Where the error occurs:
Setup in a different AWS account:
Steps to Reproduce
Run terraform apply / destroy / apply / destroy / apply / destroy until the error is triggered.
Debug Output
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None