-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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]: aws_vpc_ipam_pool_cidr_allocation cannot be imported with description
argument without replacement
#38613
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
description
argumentdescription
argument without replacement
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. |
This functionality has been released in v5.61.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. |
Terraform Core Version
1.9.1
AWS Provider Version
5.60.0
Affected Resource(s)
aws_vpc_ipam_pool_cidr_allocation
Expected Behavior
When importing an IPAM Allocation that has been created with a
description
we expect that the resource will be imported without replacementActual Behavior
Terraform is not able to import with the
description
without replacement. When adescription
is specified, Terraform shows1 to import, 1 to add, 0 to change, 1 to destroy
. This is because the resource does not write computeddescription
to state and as a result, a specifieddescription
has a value that differs fromnull
in state. Sincedescription
is aforce_new
argument, Terraform attempts to delete the IPAM allocation and recreate it.Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
Step 1: Create an IPAM allocation in the AWS Console. At a high-level, create an IPAM -> Create an IPAM Pool in the default scope -> Create an IPAM Allocation in the IPAM pool. Create this IPAM with a
description
Step 2: Import the IPAM Allocation in Terraform with the code above
Terraform displays the following
Reason: The provider does not read the description, as a result, it shows as a
null
in the stateDebug Output
No response
Panic Output
No response
Important Factoids
No response
References
ipamPoolAllocationSet
in the responsedescription
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered: