You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having some problems with importing existing AWS accounts and then managing them through this provider. Despite importing them successfully the provider seems to
Update the existing account in-place, despite the fact that the state file already matches the changes from terraform apply
Running a terraform apply fails with a strange error
Terraform Version
Terraform v1.8.5
on linux_amd64
+ provider registry.terraform.io/idealo/controltower v1.3.0
All the configuration matches that of the state file, so there should be no resource updated in place. Then when hitting terraform apply all should run with no updates or errors
Actual Behavior
Firstly, getting configuration changes in the following, despite it matching the state file:
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
# controltower_aws_account.account will be updated in-place
~ resource "controltower_aws_account" "account" {
id = "<already existing id>"
name = "<already existing name>"
tags = {}
# (6 unchanged attributes hidden)
~ sso {
~ email = "<wrong email>" -> "<correct, already existing email>"
# (2 unchanged attributes hidden)
}
}
Then applying the changes results in:
│ Error: provisioning account <name> failed: InvalidParametersException The parent organizational unit '<OU>' is not enrolled in AWS Control Tower.
│
│ with controltower_aws_account.account,
│ on main.tf line 1, in resource "controltower_aws_account" "account":
│ 1: resource "controltower_aws_account" "account" {
despite the fact that the the parent OU is enrolled correctly. Please also note that the status of the given provisioned product in AWS is "tainted". But I am able to update it through management console. Then applying another terraform apply gives the same error and "re-taints" the provisioned product.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
I actually managed to find the solution to this. It took me updating the provisioned product in the AWS console on service catalogue. I had to reaffirm that it matched that of the terraform script, despite the fact the state file and the terraform variables were completely congruent. It actually had nothing to do with the parental organization; that was all a red-herring.
Still might be an issue because the state file seemingly didn't match that of the actual configuration of the resource. So maybe it's not importing things correctly?
Hi,
I'm having some problems with importing existing AWS accounts and then managing them through this provider. Despite importing them successfully the provider seems to
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
All the configuration matches that of the state file, so there should be no resource updated in place. Then when hitting terraform apply all should run with no updates or errors
Actual Behavior
Firstly, getting configuration changes in the following, despite it matching the state file:
Then applying the changes results in:
despite the fact that the the parent OU is enrolled correctly. Please also note that the status of the given provisioned product in AWS is "tainted". But I am able to update it through management console. Then applying another terraform apply gives the same error and "re-taints" the provisioned product.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform import controltower_aws_account.compliance_account pp-*******
terraform apply
The text was updated successfully, but these errors were encountered: