@Marvin prefect v2 job_variables can i append env vars to the job? or will it always override them?

Prefect 2.x has a feature for managing job variables within deployments, specifically in the

prefect.yaml

configuration file. When defining your job variables under the

job_variables

section, you can specify environment variables. The documentation does not explicitly clarify whether you can append to existing environment variables, but it suggests that you can use existing environment variables from your local environment by templating them into your deployment configuration. Here's a brief guide on how to set job variables: 1. Add the

job_variables

section to your deployment definition in the

prefect.yaml

file:

deployments:
   - name: demo-deployment
     entrypoint: demo_project/demo_flow.py:some_work
     work_pool:
       name: local
     job_variables:
       env:
         EXECUTION_ENVIRONMENT: staging
         MY_NOT_SO_SECRET_CONFIG: plumbus
     schedule: null

2. Deploy the flow using:

prefect deploy -n demo-deployment

3. These job variables should then be visible under the Configuration tab of the deployment in the Prefect UI. If you are considering using existing environment variables, it suggests that you can template them, indicating some level of flexibility, but specifics about appending aren't included in the snippets available. For more detailed instructions, you can view the full Prefect 2.x guide on overriding job variables here. If you have further questions about behavior not explicitly mentioned in the guide, reaching out on Prefect's community forums or Slack could provide more personalized insights.