-
Notifications
You must be signed in to change notification settings - Fork 301
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.
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
Add identity to task execution metadata #2315
Add identity to task execution metadata #2315
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2315 +/- ##
===========================================
- Coverage 83.50% 46.81% -36.70%
===========================================
Files 324 219 -105
Lines 24672 20272 -4400
Branches 3512 3600 +88
===========================================
- Hits 20603 9490 -11113
- Misses 3438 10694 +7256
+ Partials 631 88 -543 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but we can only merge this after we get a new flyteidl release.
@eapolinario with the 1.12 beta release cut, can this be merged now? |
- This is necessary due to a pending PR to upstream flytekit: flyteorg#2315 This PR hasn't been merged because a new flyteidl release had to be cut. Upstream flyteorg/flyte produce a new v1.12.0-b0 tag / release that includes the necessary flyteidl changes that can now be referenced https://github.com/flyteorg/flyte/releases/tag/v1.12.0-b0 - Once the flytekit PR merges, this custom tag / version of flytekit that we've forked will no longer be necessary - NOTE: the reference to flyteidl may not be consumed properly as a "child" transitive dependency. For instance, pip install may work, while pip install may not - depending on the toolchain involved. Signed-off-by: noahjax <[email protected]>
- This is necessary due to a pending PR to upstream flytekit: flyteorg#2315 This PR hasn't been merged because a new flyteidl release had to be cut. Upstream flyteorg/flyte produce a new v1.12.0-b0 tag / release that includes the necessary flyteidl changes that can now be referenced https://github.com/flyteorg/flyte/releases/tag/v1.12.0-b0 - Once the flytekit PR merges, this custom tag / version of flytekit that we've forked will no longer be necessary - NOTE: the reference to flyteidl may not be consumed properly as a "child" transitive dependency. For instance, pip install may work, while pip install may not - depending on the toolchain involved. - This PR is based on upstream tag v1.12.0b7 Signed-off-by: noahjax <[email protected]>
@noahjax , now that flyteidl 1.12.0 is out, can you set it as the lower bound in pyproject.toml? |
I recently left Domino and it seems that I have lost push access to repos in the |
Can do - will work to get this one in tomorrow. Thanks! |
Signed-off-by: noahjax <[email protected]> Signed-off-by: ddl-rliu <[email protected]>
Signed-off-by: noahjax <[email protected]> Signed-off-by: ddl-rliu <[email protected]>
Signed-off-by: noahjax <[email protected]> Signed-off-by: ddl-rliu <[email protected]>
Signed-off-by: ddl-rliu <[email protected]>
Signed-off-by: ddl-rliu <[email protected]>
a1ba33e
to
bc1efd9
Compare
- This is necessary due to a pending PR to upstream flytekit: flyteorg#2315 This PR hasn't been merged because a new flyteidl release had to be cut. Upstream flyteorg/flyte produce a new v1.12.0-b0 tag / release that includes the necessary flyteidl changes that can now be referenced https://github.com/flyteorg/flyte/releases/tag/v1.12.0-b0 - Once the flytekit PR merges, this custom tag / version of flytekit that we've forked will no longer be necessary - NOTE: the reference to flyteidl may not be consumed properly as a "child" transitive dependency. For instance, pip install may work, while pip install may not - depending on the toolchain involved. - This PR is based on upstream tag v1.12.0b7 Signed-off-by: noahjax <[email protected]>
- This is necessary due to a pending PR to upstream flytekit: flyteorg#2315 This PR hasn't been merged because a new flyteidl release had to be cut. Upstream flyteorg/flyte produce a new v1.12.0-b0 tag / release that includes the necessary flyteidl changes that can now be referenced https://github.com/flyteorg/flyte/releases/tag/v1.12.0-b0 - Once the flytekit PR merges, this custom tag / version of flytekit that we've forked will no longer be necessary - NOTE: the reference to flyteidl may not be consumed properly as a "child" transitive dependency. For instance, pip install may work, while pip install may not - depending on the toolchain involved. - This PR is based on upstream tag v1.12.0b7 Signed-off-by: noahjax <[email protected]>
- This is necessary due to a pending PR to upstream flytekit: flyteorg#2315 This PR hasn't been merged because a new flyteidl release had to be cut. Upstream flyteorg/flyte produce a new v1.12.0-b0 tag / release that includes the necessary flyteidl changes that can now be referenced https://github.com/flyteorg/flyte/releases/tag/v1.12.0-b0 - Once the flytekit PR merges, this custom tag / version of flytekit that we've forked will no longer be necessary - NOTE: the reference to flyteidl may not be consumed properly as a "child" transitive dependency. For instance, pip install may work, while pip install may not - depending on the toolchain involved. - This PR is based on upstream tag v1.12.0b7 Signed-off-by: noahjax <[email protected]>
- This is necessary due to a pending PR to upstream flytekit: flyteorg#2315 This PR hasn't been merged because a new flyteidl release had to be cut. Upstream flyteorg/flyte produce a new v1.12.0-b0 tag / release that includes the necessary flyteidl changes that can now be referenced https://github.com/flyteorg/flyte/releases/tag/v1.12.0-b0 - Once the flytekit PR merges, this custom tag / version of flytekit that we've forked will no longer be necessary - NOTE: the reference to flyteidl may not be consumed properly as a "child" transitive dependency. For instance, pip install may work, while pip install may not - depending on the toolchain involved. - This PR is based on upstream tag v1.12.0b7 Signed-off-by: noahjax <[email protected]>
YES - thanks @pingsutw ! |
Signed-off-by: noahjax <[email protected]> Signed-off-by: ddl-rliu <[email protected]> Co-authored-by: ddl-rliu <[email protected]> Signed-off-by: bugra.gedik <[email protected]>
Signed-off-by: noahjax <[email protected]> Signed-off-by: ddl-rliu <[email protected]> Co-authored-by: ddl-rliu <[email protected]> Signed-off-by: Jan Fiedler <[email protected]>
Tracking issue
https://github.com/flyteorg/flyte/issues/
Why are the changes needed?
For our specific use case it is critical to be able to determine the identity for the subject who launches a task.
What changes were proposed in this pull request?
Add identity to TaskExecutionMetadata. This builds on top of #2282, and relies on flyteorg/flyte#5105 to add identity to the flyteidl TaskExecutionMetadata.
How was this patch tested?