[Core feature] Make execution_id and execution_domain available for plugins · flyteorg/flyte#6308

(3 commentaires) (0 réactions) (2 assignés)Python (378 forks)batch import

enhancementgood first issuehelp wanted

Métriques du dépôt

Stars: (3 705 stars)
Métriques de merge PR: (Merge moyen 3j 8h) (114 PRs mergées en 30 j)

Description

Motivation: Why do you think this is important?

BACKGROUND

https://flyte-org.slack.com/archives/CP2HDHKE1/p1741181647724639

ISSUE

We are trying to fetch Flyte execution domain in a Spark task running in Databricks using the Fyte Databricks plugin.

We tried to use the same method that works well in Python tasks running on K8s (flytekit.current_context().execution_id.domain)

Unfortunately, this approach does not work in case of Databricks plugin. It would be nice to pass this info in the API so that we can access it in tasks.

Goal: What should the final outcome look like, ideally?

We are able to fetch execution domain in tasks.

Describe alternatives you've considered

Pass the domain as workflow input param.

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

Have you read the Code of Conduct?

Guide contributeur

Direction de recherche: Analysez comment le contexte d'exécution est actuellement transmis aux plugins, en particulier le plugin Databricks. Identifiez où execution id et domain manquent et modifiez l'API du plugin pour les propager.
Stack technique: python
Domaine: backendcloud
Type d'issue: Fonctionnalité
Difficulté: 3
Temps estimé: 1-2 jours
Statut d'activité: Active
Clarté: Plutôt claire
Prérequis: PythonFlyte basics
Accessibilité débutant: 50