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

Cloud Run V2 work pool's cloudSqlInstance should be cloud_sql_instance #16460

Open
EmilRex opened this issue Dec 19, 2024 · 0 comments
Open

Cloud Run V2 work pool's cloudSqlInstance should be cloud_sql_instance #16460

EmilRex opened this issue Dec 19, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@EmilRex
Copy link
Contributor

EmilRex commented Dec 19, 2024

Bug summary

Though I don't fully understand why, it's clear that prefect-gcp's cloud run v2 work pool config for cloudSqlInstance should be cloud_sql_instance as in #16382. A user who was trying to attach a cloud SQL instance to their cloud run job was seeing the following error:

Invalid JSON payload received. Unknown name "cloudSqlInstance" at 'job.template.template.volumes[0]'

Having them install directly from the branch in #16382 resolved the issue and they were able to connect to their cloud SQL instance.

Version info

Version:             3.1.1
API version:         0.8.4
Python version:      3.10.14
Git commit:          6b50a2b9
Built:               Fri, Nov 8, 2024 12:38 PM
OS/Arch:             darwin/x86_64
Profile:             ephemeral
Server type:         cloud
Pydantic version:    2.8.2
Integrations:
  prefect-docker:    0.6.2
  prefect-gcp:       0.6.3

Additional context

No response

@EmilRex EmilRex added the bug Something isn't working label Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant