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

aws_ssoadmin_managed_policy_attachment ability to support multiple policies in single TF resource #17107

Closed
plynch-magnolia opened this issue Jan 14, 2021 · 2 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/ssoadmin Issues and PRs that pertain to the ssoadmin service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.

Comments

@plynch-magnolia
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

In the new aws_ssoadmin_managed_policy_attachment resource there is presently only support for one managed policy per resource. I am proposing the managed_policy_arn accept a list of values as there could easily be multiple managed policies to attach. In the current solution, you have to create a new TF resource for each policy you want to attach to a role.

New or Affected Resource(s)

  • aws_ssoadmin_managed_policy_attachment

Potential Terraform Configuration

resource "aws_ssoadmin_managed_policy_attachment" "role_policy" {
  instance_arn = aws_ssoadmin_permission_set.sre_sso.instance_arn
  managed_policy_arn = [
    "arn:aws:iam::aws:policy/IAMFullAccess", 
    "arn:aws:iam::aws:policy/AmazonS3FullAccess", 
    "arn:aws:iam::aws:policy/AWSLambda_FullAccess"]
  permission_set_arn = aws_ssoadmin_permission_set.sre_sso.arn
}

References

@plynch-magnolia plynch-magnolia added the enhancement Requests to existing resources that expand the functionality or scope. label Jan 14, 2021
@ghost ghost added the service/ssoadmin Issues and PRs that pertain to the ssoadmin service. label Jan 14, 2021
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Jan 14, 2021
@breathingdust breathingdust removed the needs-triage Waiting for first response or review from a maintainer. label Sep 16, 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 27, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 30, 2024
Copy link

github-actions bot commented Mar 1, 2024

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 Mar 1, 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/ssoadmin Issues and PRs that pertain to the ssoadmin 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

2 participants