-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 Cloud Functions IAM, document private-by-default by 2019/11/01 #3944
Comments
This isn't technically a breaking change for Terraform, but it is from the API. |
Hello @rileykarson , I see this issue is currently unassigned. Has there been any discussions pertaining to working on this issue? |
We have nobody actively assigned yet, but we're aware of the severity of the issue and will ensure that we provide IAM support for a reasonable window before the API-side change. |
Hi @rileykarson / @emilymye , |
Ah- looks like we didn't close this issue out or link the appropriate PRs. Sorry about that! We've supported the appropriate IAM resources since GoogleCloudPlatform/magic-modules#2297 added support for IAM resources while GoogleCloudPlatform/magic-modules#2321 added the docs. The correctly formatted example on this page shows how to create a public fn post-change: https://www.terraform.io/docs/providers/google/r/cloudfunctions_function.html I'll put out a change fixing the formatting on the page. |
fantastic, thanks @rileykarson |
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! |
Community Note
Description
On Nov 1, 2019 Cloud Functions will go private by default. We should add IAM support and get users ready for the switch far in advance.
New or Affected Resource(s)
The text was updated successfully, but these errors were encountered: