feat: Add enroll-netdev Argo workflow to enroll network devices PUC-1761#2144
Merged
Conversation
dcaa633 to
b550e3a
Compare
skrobul
approved these changes
Jul 16, 2026
b550e3a to
0704c1a
Compare
skrobul
approved these changes
Jul 16, 2026
This file contains hidden or 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
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.
Implemented
enroll-netdevWorkflowTemplate and Python entrypoint following theenroll-serverpattern.Validated in iad-dev by pointing rax-dev-iad3-dev-argo-events-workflows at this branch and using the pr workflow image.
Happy Path Log
Test evidence:
argo -n argo-events submit --from wftmpl/enroll-netdev.category=networkswitch_id=00:00:00:00:00:00switch_infoport_idphysical_networkAlso tested failure behavior:
Known limitation:
follow-up:
Can we keep this PR scoped to the current Jira requirement of two required ports, and create a follow-up to:
port1andport2?