Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Housekeeping] Store execution namespace in execution closure #3705

Closed
2 tasks done
katrogan opened this issue May 22, 2023 · 0 comments · Fixed by flyteorg/flyteadmin#568
Closed
2 tasks done

[Housekeeping] Store execution namespace in execution closure #3705

katrogan opened this issue May 22, 2023 · 0 comments · Fixed by flyteorg/flyteadmin#568
Assignees
@katrogan
Labels
housekeeping Issues that help maintain flyte and keep it tech-debt free

Comments

@katrogan
Copy link
Contributor

Describe the issue

Not all execution parameters are currently captured in the closure which makes it difficult to reason about the execution after the fact.

What if we do not do this?

Lose execution-time parameters permanently

Related component(s)

flyteidl, flyteadmin

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

  • Yes

Have you read the Code of Conduct?

  • Yes
@katrogan katrogan added the housekeeping Issues that help maintain flyte and keep it tech-debt free label May 22, 2023
@katrogan katrogan self-assigned this May 22, 2023
This was referenced May 22, 2023
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@katrogan katrogan

Labels
housekeeping Issues that help maintain flyte and keep it tech-debt free
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Save execution namespace in system metadata flyteorg/flyteadmin
1 participant
@katrogan