Skip to content
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

Retrieve AWS Organization Account Tags #14153

Closed
mr-brody opened this issue Jul 12, 2020 · 2 comments
Closed

Retrieve AWS Organization Account Tags #14153

mr-brody opened this issue Jul 12, 2020 · 2 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. new-data-source Introduces a new data source. service/organizations Issues and PRs that pertain to the organizations service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.

Comments

@mr-brody
Copy link

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

Description

We are currently using AWS organizations and using tags for downstream operations to handle different environment configurations. I think it would be a helpful feature to support a datasource of the specific account within an organization similar to its resource type and also a feature that allows for based filtering on tags. I see there are a couple API calls that should be able to support this feature:

New or Affected Resource(s)

  • Datasource: aws_organizations_account

References

Are there any other GitHub issues (open or closed) or pull requests that should be linked here? Vendor blog posts or documentation? For example:

@mr-brody mr-brody added the enhancement Requests to existing resources that expand the functionality or scope. label Jul 12, 2020
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Jul 12, 2020
@ewbankkit ewbankkit added new-data-source Introduces a new data source. service/organizations Issues and PRs that pertain to the organizations service. and removed needs-triage Waiting for first response or review from a maintainer. labels Jul 12, 2020
@github-actions
Copy link

github-actions bot commented Jul 3, 2022

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 github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Jul 3, 2022
@github-actions github-actions bot closed this as completed Aug 2, 2022
@github-actions
Copy link

github-actions bot commented Sep 2, 2022

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. new-data-source Introduces a new data source. service/organizations Issues and PRs that pertain to the organizations service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants