-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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]: Import on aws_organizations_account will force a recreation if iam_user_access_to_billing was already set #35661
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Makes use of the latest framework to implement a backwards compatible import, that allows you to specify the state of aws_organizations_account. Addresses hashicorp#35661
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.50.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.7.0
AWS Provider Version
5.31.0
Affected Resource(s)
aws_organizations_account
Expected Behavior
When running
import aws_organizations_account.this 11111111111
on an account where iam_user_access_to_billing was set, the resource should be imported cleanly.Actual Behavior
iam_user_access_to_billing is imported into the state file as null, meaning TF will try and set it, forcing a re-creation.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
N/A
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
The AWS describe account API does not return iam_user_access_to_billing, so custom logic will be needed in the import step to be able to pass the state of this
References
https://docs.aws.amazon.com/organizations/latest/APIReference/API_DescribeAccount.html
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: