data.aws_organizations_organization doesn't pull all accounts when used from child account

[rnikoopour]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform v0.15.3
on darwin_amd64

• provider registry.terraform.io/hashicorp/aws v3.58.0

Affected Resource(s)

• data.aws_organizations_organization

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

terraform {}
provider "aws" {region = "us-west-2"}
data "aws_organizations_organization" "org" {}

output "org" {
  value = data.aws_organizations_organization.org
}

Debug Output

N/A

Panic Output

N/A

Expected Behavior

When using a child account to run the terraform I expect to see all my organizations accounts in data.aws_orgnizations_organization.org.accounts just like I do when I call aws organizations list-accounts.

Actual Behavior

data.aws_orgnizations_organization.org.accounts is null

Steps to Reproduce

1. Log into child account cia the CLI
2. terraform apply the above hcl

Important Factoids

Adding to the account fields in blocked by requiring the terraform to be running as the root account:

terraform-provider-aws/aws/data_source_aws_organizations_organization.go

Line 159 in 118137c

if aws.StringValue(org.Organization.MasterAccountId) == meta.(*AWSClient).accountid {

References

N/A

[cob16]

This looks to be a duplicate of #18590

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.