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 org policies at the organization level #507

Closed
rosbo opened this issue Oct 2, 2017 · 1 comment · Fixed by #523
Closed

Add support for org policies at the organization level #507

rosbo opened this issue Oct 2, 2017 · 1 comment · Fixed by #523
Assignees

Comments

@rosbo
Copy link
Contributor

rosbo commented Oct 2, 2017

Organization policies provide the following benefits:

  • Policies can be set per project or per organization.
  • Policies are inherited down the resource hierarchy, and can be overridden at any level on which an org policy can be set.
  • Policies are not necessarily managed by the owner of the resource. Instead, policies are managed by your organization's policy administrator (IAM role: roles/orgpolicy.policyAdmin). This means that individual users and project owners cannot override policies.

https://cloud.google.com/resource-manager/docs/organization-policy/overview

@rosbo rosbo self-assigned this Oct 2, 2017
@rosbo rosbo closed this as completed in #523 Oct 5, 2017
luis-silva pushed a commit to luis-silva/terraform-provider-google that referenced this issue May 21, 2019
<!-- This change is generated by MagicModules. -->
/cc @rileykarson
@ghost
Copy link

ghost commented Mar 30, 2020

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 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants