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

Flyte

<@U06RKAMK0UC> can I get the targeted `domain` from the flyte context?

Yes, you can retrieve the targeted `domain` from the Flyte context using `flytekit.current_context().execution_id.domain`. This method allows you to access the domain information at runtime within a task.

Would you like more detail on how to implement this in your code?

Sources:
- <https://discuss.flyte.org/t/15971715/hey-everyone-i-m-new-to-flyte-and-im-looking-to-add-logic-to/|Flyte Discussion on Retrieving Domain>
- <https://discuss.flyte.org/t/44076/how-can-i-get-workflow-metadata-at-runtime-these-days-projec/|Flyte Discussion on Workflow Metadata> :+1: 0 button :-1: 0 button 💡 *Hint:* Mention @runllm in the thread for followups.

<@U06RKAMK0UC> That returns `local` and not the value passed in from CLI `--domain`

The behavior you're experiencing might be due to running the task locally. When running tasks locally, Flyte defaults to using "local" as the domain. To ensure the correct domain is used, you should run the task in a remote environment where the domain is set correctly.

Would you like more detail on how to configure your environment to reflect the correct domain?

Sources:
- <https://discuss.flyte.org/t/16719573/does-flyte-expose-some-kind-of-flag-to-indicate-if-a-workflo/|Flyte Discussion on Local vs Remote Execution> :+1: 0 button :-1: 0 button 💡 *Hint:* Mention @runllm in the thread for followups.