Skip to content
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

Missing Data and Erroring command #82

Open
hodgiepodgie opened this issue Apr 12, 2024 · 3 comments
Open

Missing Data and Erroring command #82

hodgiepodgie opened this issue Apr 12, 2024 · 3 comments

Comments

@hodgiepodgie
Copy link

I was told that the product was GA now. I have updated to the 1.0 release and have been playing around with the commands a bit. I thought I would update you on a couple of different things that I observed while using some of the commands.

When running a get-rscvsphereVm command and plugging it into a variable. like
$vm = get-rscvsphereVm -Name Server1
$vm
Name Operating System SLA Domain RBS Status Id


Server1 Microsoft Windows Server 2016 or later (64-bit) 30_Day_VM_Image 0950dcb3-5bf4-5c3c-8884-2ce78e33e526
Server1 Microsoft Windows Server 2016 or later (64-bit) 30_Day_VM_Image 49fbb582-f432-501c-b0b9-357ab24274e2
Server1 Microsoft Windows Server 2016 or later (64-bit) 66a0c677-ac9e-5e2c-a7e9-472a152d670b

I will get multiple entries back since my vCenter is matched to multiple clusters. Since the cluster is not shown in this view, I am unable to tell at a glance what cluster the backups were on.

However, if I dig into the variable with $vm | fl, I can see that you have a lot of data underneath the hood. However, I noticed most of those entries were blank. I did however, find the clusterid and was able to write another command to match the id to the name but it looks like you guys intend/intended to have a lot of this data here already. I am sure this is still being developed but wanted to make sure it was not just an issue on my part.

Next, I followed the get-help on command get-rscsnapshot
Even using the examples in the get-help, this command comes back with errors so long it doesn't even fit on the terminal scroll back. If you would like me to show you what I am running into, let me know.

@guirava
Copy link
Collaborator

guirava commented Apr 17, 2024

Thank you for your feedback, we identified that get-rscvsphereVm needs to be deprecated - sorry you ran into issues using it . Please use Get-RscVmwareVm instead and let us know if it works for you .

As for the empty fields:

The SDK tries to identify what fields should be in the response, and selects a minimal set of fields doing so .
We welcome feedback on what that set of fields is.
Please feel free to get back to us with what fields you feel should be in that response and we will add them to the default response.

@hodgiepodgie
Copy link
Author

hodgiepodgie commented Apr 18, 2024 via email

@GronTron
Copy link

Hello,
In response to this I'd like to provide feedback on a property.
The Get-RscVmwareVm cmdlet has a property labeled "SlaAssignment"
When running this command against a VM that inherits it's SlaDomain, the field only displays the "DERIVED" value. Can you change this so it will display the name of the SLA domain instead? Alternative suggestion would be to have two different properties. SlaAssignmentType (displays how the Sla is applied IE Direct, Derived etc.) and SlaAssignment (displays the name of the SLA domain)
Second, also in Get-RscVmwareVM, add value to the property for VsphereTagPath. I would suggest displaying this as such:
RubrikClusterName/vCenterServerName/vSphereTagCategory/TagName
Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants