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 tested the SSO Module in a test AWS Orgnization which had 2 AWS Accounts with the same name, both were called Development, yet seperate accounts.
As AWS does not protect against this, it seems a rare but possible scenario. When I run terraform plan the issue presents itself like so;
│ Error: Duplicate object key
│
│ on .terraform/modules/aws-iam-identity-center/locals.tf line 127, in locals:
│ 126: accounts_ids_maps = {
│ 127: for idx, account in data.aws_organizations_organization.organization.accounts : account.name => account.id
│ 128: if account.status == "ACTIVE" && can(data.aws_organizations_organization.organization.accounts)
│ 129: }
│ ├────────────────
│ │ account.name is "Development"
│
│ Two different items produced the key "Development" in this 'for' expression. If duplicates are
│ expected, use the ellipsis (...) after the value expression to enable grouping by key.
Is it possible to account for this at the module level?
Regards
The text was updated successfully, but these errors were encountered:
I tested the SSO Module in a test AWS Orgnization which had 2 AWS Accounts with the same name, both were called Development, yet seperate accounts.
As AWS does not protect against this, it seems a rare but possible scenario. When I run
terraform plan
the issue presents itself like so;Is it possible to account for this at the module level?
Regards
The text was updated successfully, but these errors were encountered: