-
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
aws_organizations_organization feature_set change should not force new resource #15462
Comments
Looks like it's possible to do this, although once you enable All Features it can't be reverted. I'd be interested in attempting to solve this if that's alright? |
@philnichol yep I believe that is the case. I just put a PR up for the fix here if you'd like to comment: #15473 |
@ryandeivert your solution is 1000x more elegant than what I was thinking :) didn’t even know about ForceNewIfChange, nice one! |
…zation-15462 adding fix for aws org feature_set update issue from #15462
The proposed fix has been merged and will release with version |
This has been released in version 3.16.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 for triage. Thanks! |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Terraform CLI and Terraform AWS Provider Version
Terraform version: 0.13.1
AWS Provider version: 3.9.0
Affected Resource(s)
aws_organizations_organization
Terraform Configuration Files
When updating the following resource from the "before" to "after", terraform the following
org
resource from:Before
After
Debug Output
Panic Output
Expected Behavior
The change to
feature_set
does not force a new resource, which would generate a new Org ID. The feature set can be changed in Console without creating a new org ID, and I was informed by AWS that this should not need to generate a new org ID.Actual Behavior
A new resource if forced when
feature_set
is changed fromCONSOLIDATED_BILLING
toALL
. This should only force a new resource if going fromALL
toCONSOLIDATED_BILLING
, according to this note on this page:Steps to Reproduce
terraform apply
using the config aboveImportant Factoids
References
N/A
The text was updated successfully, but these errors were encountered: