feat: handle priority for golden records from the orchestrator #1156
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
…ssing' into feat-priority-based-record-processing
|
@nicoprow @SujitMBRDI I've raised this PR just to get some feedback. It's still a work in progress, so feel free to share your thoughts! |
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.
Description
This PR implements priority handling (High, Low) based on thresholds within the orchestrator. It also adds new endpoints for registering gate components with priorities. The orchestrator will generate the
OriginIdautomatically and that will be used by the gate component.Issue: eclipse-tractusx/sig-release#856
Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review: