-
Notifications
You must be signed in to change notification settings - Fork 3
[LINK-5243]: Add ability to export System Discovery Results via CLI #493
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
michaelfarrell76
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sik
blevine-transcend
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sweet! do we want to include or filter on status? potentially good to know, as i believe these results will include ones already to added to inventory
Ah yeah you are right, adding status makes sense here! I am not sure how to add a filter just yet, but will amend this PR to add status for now. |
| @@ -0,0 +1,19 @@ | |||
| siloDiscoveryResults: | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh crap i missed this, i think our top level keys are in dash case, can we change to just system-discovery
Description
New system Discovery UI uses updated backend, need to add ability for user to be able to export silo discovery result using CLI.
This PR implements pull functionality.
Based of #380 PR
Related Issues
Demo(s)
Added SD on local BE instance and executed CLI pointing to local
Result