-
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
[WIP] Add an aws_organizations_account_ids data source #4384
Conversation
I'll get the conflicts and the test failure fixed tonight. |
Tested this on an account with many accounts in an organization and it's working fine. |
6d17c92
to
87f1869
Compare
Hi, Has there been any more movement on this? Cheers, |
It is almost a year ago, there are several pull requests open, when we finally can expect the accounts data sources to be released? |
any update on this? |
Now that #571 has been merged, can we get this included? |
Hi @breser 👋 Thank you very much for your time and contribution here. My apologies for the long silence on this pull request. The support for AWS Organizations has been quite the long process and there were differing implementations offered by various members of the community. In the future, we am hoping that we can host these type of implementation discussions in design issues where the implementation choice is agreed on before we wind up in the same situation of conflicting contributions. After evaluating all the contributions, we decided to opt for a single
This new We really appreciate the time and effort that went into this contribution and we hope to be able to work with you again in the future. |
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! |
Part of #571
Corresponds to ListAccounts and the ListAccountsForParent APIs. Motivation here is to be able to write IAM policies that automatically allow things for all accounts in an Organization or Organizational Unit (e.g. allowing all accounts belonging to an Organization to write CloudTrail logs to the same S3 bucket) without needing to hardcode the Account Ids.
I have not written the tests for this yet because to do so I really need #4207 and #4229. But I wanted to checkpoint my work and get feedback on what I already have.
I've tested it as follows:
Which resulted in the following output (actual account id obfuscated):
With the root id:
Which resulted in the following output (actual account id obfuscated):
I then moved the account into an OU and tried it again with the root which resulted in the following output (actual account id obfuscated):
And then finally with the OU id:
Which resulted in the following output (actual account id obfuscated):
I intend to test with an account with many accounts in the Organization next week at work.