@Marvin: are prefect settings accessible from with the pull steps of a deployment?

To answer your question regarding accessing Prefect settings from within the pull steps of a deployment, the documentation primarily focuses on defining pull actions within the

prefect.yaml

file. Here is the relevant piece of information from the Prefect deployment guide:

The

pull

action is used to define how Prefect will pull your deployment in remote execution environments. Each action is defined as a list of steps that are executed in sequence.

Each deployment step can provide a

requires

field for auto-installation and can optionally specify an

id

for referencing step outputs in later steps. Additional fields map directly onto Python keyword arguments to the step function. Sadly, there's no explicit mention of accessing Prefect settings directly within these steps. 1. Documentation Reference: Prefect Deployment Configuration Guide 2. Related GitHub Issues: - One user faced issues specifically with HTTP private repositories in pull actions, which may indirectly relate to access settings in specialized environments (e.g., private repos and credentials). GitHub Issue #13111 - There were some concerns about private access tokens being exposed in logs, possibly related to storage and retrieval settings. GitHub Issue #8310 In conclusion, while the

pull

action configuration is quite flexible, direct access to Prefect settings within pull steps isn’t explicitly documented. Instead, you can configure your steps using defined settings and resources within the

prefect.yaml

structure.

hi @benorbital - what are you trying to do?

oh, it was just a harebrained scheme I had in mind for bypassing the issue of selectively overriding environment variables