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

Add support for managing only AuditConfig in IAM policy #3084

Closed
marcin-kolda opened this issue Feb 19, 2019 · 3 comments
Closed

Add support for managing only AuditConfig in IAM policy #3084

marcin-kolda opened this issue Feb 19, 2019 · 3 comments

Comments

@marcin-kolda
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 "me too" comments, 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. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

Currently auditConfigs can be only configured using google_iam_policy data source, which requires binding in IAM policy as well. We would like to configure auditConfigs without IAMs (they would be configured separately) or with using google_project_iam_member resource.

New or Affected Resource(s)

  • google_project_iam_audit_config

Potential Terraform Configuration

Terraform configuration should be the same as audit_config part in google_iam_policy data source.

References

@ghost ghost added the enhancement label Feb 19, 2019
@paddycarver
Copy link
Contributor

We actually have support for that in 2.0.0, I was just neglectful and forgot to document it on the website. (See #3066.) I'll get that info up on the website.

@rileykarson
Copy link
Collaborator

I'm going to close this as a dupe of #3066 since that tracks adding the docs, and the fine-grained resource already exists.

If you're interested in managing this on non-project IAM policies (eg org, billing, subnetwork, etc) please file another issue! (And let me know if I closed this in error.)

@ghost
Copy link

ghost commented Mar 28, 2019

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. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants