-
Notifications
You must be signed in to change notification settings - Fork 127
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
VPC Connector throws error during deployment #277
Comments
@JonasLaux vpc property does work for me, but I referenced different test feels like when full path is provided 'projects/PROJECT_ID/locations/us-central1/connectors/CONNECTOR_NAME' - google handles it as "custom" connector |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey,
we're currently trying to attach onto our Cloud Functions our Memorystore. Therefor we need a VPC-Connector. In the plain gcloud CLI this would look something like this:
gcloud functions deploy myFunction --vpc-connector myVPCConnector
To accomplish this, we could not find anything in the documentation, though found some tests here that had this functionality.
So we added our vpc connector in our yaml file to our function, but we only get the following error during "sls deploy":
{ "ResourceType":"gcp-types/cloudfunctions-v1:projects.locations.functions", "ResourceErrorCode":"400", "ResourceErrorMessage":{ "code":400, "message":"The request has errors", "status":"INVALID_ARGUMENT", "details":[ { "@type":"type.googleapis.com/google.rpc.BadRequest", "fieldViolations":[ { "field":"vpc_connector", "description":"A Cloud Function and a Serverless VPC Access connector must be located in the same region." } ] } ], "statusMessage":"Bad Request", "requestPath":"https://cloudfunctions.googleapis.com/v1/projectsmyGCPProject/locations/europe-west1/functions/myFunction", "httpMethod":"PATCH" } }
Though the VPC connector and the function are in the same region. Also, if i add it manually via the Cloud Console web interface it works (but ofc after redeployment, this change is gone)
The text was updated successfully, but these errors were encountered: