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

Feature request add filtering to aws_iam_role #17868

Closed
adamstirk-ct opened this issue Mar 1, 2021 · 4 comments
Closed

Feature request add filtering to aws_iam_role #17868

adamstirk-ct opened this issue Mar 1, 2021 · 4 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/iam Issues and PRs that pertain to the iam service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.

Comments

@adamstirk-ct
Copy link
Contributor

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

It would be useful to be able to filter IAM roles using datasource filtering as per https://registry.terraform.io/providers/hashicorp/oci/latest/docs/guides/filters.

In our use case we use AWS Control Tower which creates AWS SSO roles which are unique and we currently have no way of getting the roles without first storing it somewhere first (e.g. variable or SSM parameter).

New or Affected Resource(s)

  • aws_iam_role

Potential Terraform Configuration

data "aws_iam_role" "example" {
	filter {
		name = "name"
		values = ["AWSReservedSSO_AWSAdministratorAccess_*"]
	}
	
	filter {
		name = "path"
		values = ["/aws-reserved/sso.amazonaws.com/eu-west-1/"]
	}
}
@adamstirk-ct adamstirk-ct added the enhancement Requests to existing resources that expand the functionality or scope. label Mar 1, 2021
@ghost ghost added the service/iam Issues and PRs that pertain to the iam service. label Mar 1, 2021
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Mar 1, 2021
@bplotnick
Copy link

I think this is a dupe of #14470, which is addressed in #18585 (PR in review)

@jlamande
Copy link

Yes the #18585 is still open and waiting for any review

@breathingdust breathingdust removed the needs-triage Waiting for first response or review from a maintainer. label Sep 4, 2021
Copy link

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 Dec 17, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 18, 2024
Copy link

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 Feb 18, 2024
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. service/iam Issues and PRs that pertain to the iam service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

No branches or pull requests

4 participants