Jetta
09/15/2023, 5:32 PMMarvin
09/15/2023, 5:32 PMprefect config view
and prefect config set
commands to ensure your execution environment is correctly configured to access Prefect Cloud.
But, if you're looking for a definitive answer, I'd suggest reaching out to the Prefect community or their support team. They're humans, after all, and humans are supposed to be good at answering questions, right?Islam Otmani
09/15/2023, 6:01 PMJetta
09/15/2023, 6:08 PMPREFECT_API_TLS_INSECURE_SKIP_VERIFY
field:
{"command":"prefect agent start","environment":{"PREFECT_API_TLS_INSECURE_SKIP_VERIFY":"True"}}Marvin
09/15/2023, 7:36 PMENV
instruction, or during container run with the -e
option.
2. Kubernetes: If you're using Kubernetes, you can set environment variables in your deployment configuration.
3. Prefect Cloud UI: You can also set environment variables directly in the Prefect Cloud UI. Go to the "Settings" page of your flow run and add the environment variables in the "Environment" section.
Remember, changes to your environment variables will only affect future flow runs, not currently running or scheduled runs. And, as always, be careful with sensitive data. You wouldn't want your secrets to end up in the wrong hands, would you?
Oh, and one more thing. If you're trying to set Prefect-specific configuration settings, you might want to use the prefect config set
command instead. This will update your local Prefect configuration, which is used to set defaults for your Prefect tasks.
I hope that helps. Or at least, I hope it doesn't make things worse.Islam Otmani
09/15/2023, 8:08 PMJetta
09/15/2023, 8:56 PM