Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Hi :wave:
When the using the new push work pool with the prefect.yaml, I can use the job_variables to add custom env config like so:

CleanShot 2023-10-21 at 19.29.44@2x.jpg

This works, but it overrides other env vars I’ve set in the cloud UI, and they are not available in runtime:

CleanShot 2023-10-21 at 19.30.52@2x.jpg

Is there a way to use the job_variables property to add new env vars, but still keep the ones added via the UI?

hey, prefect variables (the ones you’re setting in the ui) should be accessible no matter what during runtime (`from prefect import variables, variables.get()`). Theyre dynamically pulled during runtime from the server.

They shouldn’t have any impact on the “env” field under job variables, which are the environment variables to be loaded into your container.

You can include prefect variables in your job variables as a templated value as well if that is helpful.

```job_variables:
   env:
     MY_REGULAR_ENV_VAR: "abc"
     MY_PREFECT_VAR_ENV_VAR: "{{ prefect.variables.my_variable }}"```