https://prefect.io
Join Slack
Has anyone had an issue with env vars not getting passed from the agent to the job with a kubernetes...
# ask-community
a
Has anyone had an issue with env vars not getting passed from the agent to the job with a kubernetes run leveraging 
PREFECT__CLOUD__AGENT__ENV_VARS
agent variable?
b
Hi Alex, here are a few follow up questions: • Are you getting a specific error? • What is your use case?
a
I am trying to pass environment variables whos contents are managed within IaC to also be passed into the flow execution that way. I don't want my data engineers to need to know anything about IaC when working within our systems
The agent is being deployed as version 1.0.0 as we are migrating from ecs to kubernetes. I am am trying not to change compatibility. I am using this variable as documented in the help text
Copy code
-e, --env TEXT                 Environment variables to set on each
                                 submitted flow run.
the command I used to generate the deployment was the 
prefect agent kubernetes install
with the -env. There wasn't any documentation and I used the errors from the flow deployment to help me understand. I had variables getting passed in, but I did not check to see how they were getting passed. Now I have an error when trying to use ENV variables in a dbt metadata file.
b
Can you provide and example of how you're using the --env call? Also, here's an article that outlines how to use --env for setting secrets, which is done in a similar fashion.
Also the syntax in the yaml for the agent deployment will appear something like this:
Copy code
- name: PREFECT__CLOUD__AGENT__ENV_VARS
          value: '{"test": "test2"}'
4 Views
Open in Slack
PreviousNext
Powered by

Prefect Community

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.

Powered by