[WIP] feature: support argo retry #2277
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
A known limitation for this solution would be:
We are planning to address this limitation by making MAX_ATTEMPTS configurable via envvar. |
dhpikolo
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR, modifies the step cli command to infer retry_count from flow_datastore class. Looks like this class, holds all the information about underlying datastore and run artifacts.
flow_datastoreclass method that infers latest done attempt of a task.MF_ATTEMPTfrommflog.save_logspython script and infer attempt from the datastore.Resolves: #2278