@Marvin can a work pool obtain env vars from a secret block?

From the searches in Prefect documentation, here's what I found: 1. Prefect 2.x: - The Prefect 2.x documentation indicates that job variables, including environment variables, can be overridden per deployment or per flow run. However, there is no explicit mention in the search results about directly sourcing these variables from a secret block. For more details, you can refer to the overriding job variables guide. 2. Prefect 3.x: - Similar to 2.x, Prefect 3.x documentation mentions that work pools can utilize environment variables, but it doesn't explicitly state that these can be obtained from a secret block. However, Prefect supports secret management through blocks like

SecretStr

and

SecretDict

to securely handle sensitive information. - For more details, you can check the infrastructure concepts for work pools and block documentation. If you need to use secrets in your environment variables, you can manually fetch secrets in your flow code and then set them as environment variables programmatically. For more precise guidance, you could explore Prefect's extensions or community examples that implement this pattern, as the official documentation might not cover direct integration of secret blocks into work pool environment variables.

tldr, yes you can template in secret blocks or variables in either • job overrides (override work pool config for a deployment or flow run) • on the work pool base job template itself

@Nate do you have an example of templated secret block?

thank you!

note that this example will render the secret at deployment time https://github.com/PrefectHQ/prefect/issues/15489

@Nate does this work for prefect v2?

yes! this works the same in 2 and 3