Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Currently, when getting the `domain` from the context(via `execution_id`) I get `local` if the workflow was triggered locally. I want a way to get the value of `-d` flag that tells flyte which domain to register the workflow. Can I do this somehow programatically?

so even in local execution, if you pyflyte run -d … you want to pick it up?

Yea because I want to know which domain the project is running in

but in local execution there’s no real domain cuz there’s no real flyte backend.

you can read it though - it’s fed in through <https://github.com/flyteorg/flytekit/blob/e9a7da19fe50e6588ec3a66a44a8724a9e96e8cd/flytekit/clis/sdk_in_container/run.py#L94|here> in the case of `run`

can be picked up in run_level_params, and passed all the way down.  and `local` is not too meaningful, i can’t believe people depend on this behavior, so if you want to change it so that domain is respected when local runs are made with the -d flag, i’m sure we’d accept it.

ok cool. Yea our use case is a little watchdog task that queries the flyte db and checks for things that have schedules but haven't executed in some configured time. For us, it's important that we are only querying the same domain and not allow cross domain