@Marvin hello. do you have the environment variable list for prefect 0.15.13?

You can find the environment variables for Prefect 0.15.13 in the Prefect documentation. Some of the key environment variables include: - `PREFECT_LOGGING_LEVEL`: Controls the logging level, e.g., 'DEBUG'. - `PREFECT_PROFILE`: Specifies the active profile, e.g., 'default'. - `PREFECT_AGENT_PREFETCH_SECONDS`: Sets the agent's prefetch seconds, e.g., '10'. - `PREFECT_AGENT_QUERY_INTERVAL`: Sets the agent's query interval, e.g., '5.0'. - `PREFECT_API_KEY`: API key for authentication. - `PREFECT_API_REQUEST_TIMEOUT`: Timeout for API requests, e.g., '60.0'. - `PREFECT_API_URL`: URL for the Prefect API, which can be set to a local server or Prefect Cloud. You can view and modify these settings using the Prefect CLI with commands like

prefect config set

and

prefect config unset

.

@Marvin hmm ok. How can I use the env vars that use two underscores? Like PREFECT___SERVER___HOST

It seems there is no direct mention of environment variables with double underscores (like

PREFECT___SERVER___HOST

) in the Prefect 0.15.13 documentation. However, these variables are typically used to denote nested configuration settings. Here's a general approach you can take: 1. Environment Variable Naming: Double underscores (

__

) in environment variable names are often used to represent nested configuration keys. For example,

PREFECT___SERVER___HOST

might correspond to a configuration setting like

server.host

. 2. Setting Environment Variables: You can set these environment variables in your shell before starting your Prefect server or running your Prefect flows. For example:

bash
   export PREFECT___SERVER___HOST='your_host_value'

3. Using Prefect CLI: Ensure that your Prefect server or agent is started after setting these environment variables so that they are picked up correctly. For more details, you might want to explore the Prefect settings documentation.