Support device in non-default namespace #238
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
Haishi2016
approved these changes
Apr 30, 2024
msftcoderdjw
approved these changes
May 1, 2024
Haishi2016
pushed a commit
that referenced
this pull request
May 15, 2024
* Support device in non-default namespace * fix missing argument in test * handle missing namespace field * Fix provisiongingStatus missing error in target update
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.
Changes
Test
Manually created devices in non-default namespaces. And then launch symphony agents to take snapshots on those devices and report status back to symphony devices and targets.