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

Flyte

Hi, I have a question: Is there a way from within a task code execution to retrieve information on under what domain &amp; project is it running. on? E.g. I have Development/Staging/Production domains, and when I run the workflow, I want task to load configs for the right environment.

I'm not sure off the top of my head if flytekit offers the info as well, but you should be able to read it from the env variables of your container

there's a few being set:
```FLYTE_INTERNAL_DOMAIN
FLYTE_INTERNAL_EXECUTION_DOMAIN
FLYTE_INTERNAL_EXECUTION_ID
FLYTE_INTERNAL_EXECUTION_PROJECT
FLYTE_INTERNAL_EXECUTION_WORKFLOW
FLYTE_INTERNAL_NAME
FLYTE_INTERNAL_PROJECT
FLYTE_INTERNAL_TASK_DOMAIN
FLYTE_INTERNAL_TASK_NAME
FLYTE_INTERNAL_TASK_PROJECT
FLYTE_INTERNAL_TASK_VERSION
FLYTE_INTERNAL_VERSION```
should probably be able to grab the info from there

<@U03A7NKMWGM> is this documented somewhere? Was wondering specifically about the difference between `FLYTE_INTERNAL_DOMAIN` and `FLYTE_INTERNAL_EXECUTION_DOMAIN`

<@U03KAQL5ZU1>, you can use `flytekit.current_context().execution_id.project` construct to retrieve project; same for domain.

I figured there'd the something less hacky than reading env vars :sweat_smile:

I'm not aware of any public documentation regarding those env vars, since I believe they're just used for flytekit/flyte's internal components, but <@U01J90KBSU9> might be able to confirm that

Yeah, the env variables haven’t been documented.

&gt; difference between `FLYTE_INTERNAL_DOMAIN` and `FLYTE_INTERNAL_EXECUTION_DOMAIN`
I don’t think `FLYTE_INTERNAL_DOMAIN` exists anymore. It got to be the latter var.

both seem to existing on a recently created container in one of our flyte namespaces, but the former one is probably deprecated

<@U041L0THSDP> I’m not 100% certain, but I believe `FLYTE_INTERNAL_DOMAIN` will point to the domain the task was registered to, whereas `FLYTE_INTERNAL_EXECUTION_DOMAIN` will point to the domain the task is running in.
This makes a difference in case you run a task “by reference” (<https://docs.flyte.org/projects/cookbook/en/stable/auto/core/flyte_basics/reference_task.html|docs>) where you can e.g. run a task which was registered to `production` within the `development` domain

Thanks for the explanation <@U03C1MJQ892>

And we should document it cc <@U01DYLVUNJE> can we add it to wd-40