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.

Prefect Community

Wanted to gauge any interest in the following enhancement to the ShellTask.  We were thinking that there would be value in having the ability to access context like task_name, flow_name, etc.

Hey <@UM6AJ5V7G>, I’m having a hard time picturing what you would do. Are you trying to use context info the in command of the ShellTask?

so in dbt I can reference envars in my dbt_project.yml and other places.  This means I could potentially make use of the underlying prefect task/flow metadata.

for us the use case was isolating dbt artifacts when you are running many dbt run commands in a single flow.

or you want to have prefect flow/task run data available in the artifacts themselves.

you can try an pass them in as envars directly in the current shell task, but does not look like they are lazily evaluated that way.

Did you pass try passing them in the `run` method? I think that would lazily evaluate it