maestro consumer registration pipeline #1317
Merged
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
geoberle
requested review from
bennerv,
janboll,
jmelis,
jonathan34c,
SudoBrendan,
UlrichSchlueter,
weinong,
whober0521,
tony-schndr,
jfchevrette and
jharrington22
as code owners
janboll
previously approved these changes
Feb 13, 2025
add the maestro agent registration step to the agent installation pipeline. this way a new agent gets registered immediately with the server after installation. note: this does not imply that CS will immediately use it as a provisioning shard. this is a dedicated topic for P3 Signed-off-by: Gerd Oberlechner <[email protected]>
Signed-off-by: Gerd Oberlechner <[email protected]>
geoberle
force-pushed
the
maestro-agent-registration-pipeline
branch
from
d21897a to
aa0363c
Compare
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.
What this PR does
add the maestro agent registration step to the agent installation pipeline. this way a new agent gets registered immediately with the server after installation.
note: this does not imply that CS will immediately use it as a provisioning shard. this is a dedicated topic for P3
Jira:
Link to demo recording:
Special notes for your reviewer