You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 an 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 an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.
@gal432 I am not sure what value is passed to vpc_connector, make sure its in the format projects/xxx/locations/us-central1/connectors/vpcconn. If you still get the error, please share your debug log. The following config worked fine for me
OK. the problem was when I set the connector.name instead of connector id. the cloud function did attached to the vpc_connector, but I couldn't use the vpc_connector_egress_settings.
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
locked and limited conversation to collaborators
May 28, 2020
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
V0.12.18
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Cloud function should be created with vpc_connector_egress_settings ALL_TRAFFIC
Actual Behavior
Error 400 from google
Important Factoids
References
When I took a look in the code I see that we used ALL_TRAFFIC in
#5984
but in the docs it should be all
https://cloud.google.com/sdk/gcloud/reference/functions/deploy#--egress-settings
The text was updated successfully, but these errors were encountered: