@Marvin We're using prefect cloud and running jobs on cloud run in gcp. prefect-gcp version 0.5.6 contains some changes to how the vpc_connector_name is set in the V2 job templates, but when testing this in prefect cloud it doesn't seem like the issue is fixed. Do you know if it's in any way possible to control the version of this library used in prefect cloud, or where i can file an issue to get this upgraded?

To specify the version of

prefect-gcp

or any other library used in Prefect Cloud, you should declare the version of the library within your deployment's environment. This can typically be done in your runtime environment configuration or by specifying your requirements in a

requirements.txt

file for your flow's environment. Unfortunately, the documentation doesn't specify exactly how to control library versions for Prefect Cloud specifically, but the general practice for Python environments applies. For filing an issue or inquiring about upgrading the

prefect-gcp

library, you can open a new issue on GitHub in the prefect-gcp repository. If you encounter any bugs, you are encouraged to file an issue there. Additionally, you may seek support in the Prefect Discourse forum or the Prefect Slack community if you need further assistance. Regarding the

vpc_connector_name

and its changes in the

prefect-gcp

version 0.5.6, I found no open issues in the GitHub repository with a simple search. Therefore, if this problem persists for your use-case, you may consider opening a new issue to address it. The pertinent links for further reading and support are: - To open an issue about `prefect-gcp`: prefect-gcp GitHub issues - Prefect GCP documentation: prefect-gcp Documentation If you decide to open an issue, please provide detailed information about your configuration, the steps to reproduce the issue, and any logs or error messages you have. This will help the maintainers understand and resolve the issue more effectively.