This release of prefect-gcp fixed an issue related to the placement of the vpc_connector_name in Cloud Run v2 push work pools. When testing this in Prefect Cloud with a v2 push work pool, the vpc connector name is however still not set in Cloud Run (it's showed correctly in the Prefect Cloud UI). I'm assuming the issue here is that Prefect Cloud isn't using version

>=0.5.6

of

prefect-gcp

, any chance this can be fixed? 🙏

Hi, thanks for raising this. Let me take a look

Thanks! We downgraded back to V1 for the work pool in question while we wait for the fix, works there 🙂

sounds good, I can let you know when this is live in cloud to give a try. should be out later today

Thanks!

Apologies we weren't able to release until this morning. It should be out now!

Tested now, still doesn't seem to work on our end... Do you need any more info from me to debug?

Whats your work pool id? Did you use an existing work pool or create a new one?

Tried both, neither worked... Not sure about the ID, can't see it in the URL... The name is

push-v2-static-ip-clickops-test

Are you getting an error at all? or it's just not populating? I'm able to pass a connector and see it populate on the job.

Tried again and now it seems to be working. However it only routes requests to private IP's to the VPC. Do you know where in the V2 template I can add the annotation

"<http://run.googleapis.com/vpc-access-egress|run.googleapis.com/vpc-access-egress>": "all-traffic"

?

Ah okay: • so we only elevate certain common configurations to the

Default

tab of the work pool • Anything you want to pass directly to the cloud run v2 api, you can add in the

Advanced

tab by directly modifying the job_body • based on the v2 api docs it should go here in the job body: (unsure if it's specified as an all-caps string or not):