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

PR for a bunch of open issues #687

Merged
merged 46 commits into from
Sep 11, 2020
Merged

PR for a bunch of open issues #687

merged 46 commits into from
Sep 11, 2020

Conversation

jaapbrasser
Copy link
Contributor

@jaapbrasser jaapbrasser commented Sep 6, 2020

Description

This PR fixes pretty much everything that has been reported broken. There's a lot of changes so I don't envy whoever made the mistake of picking this up for review.

Related Issue

Resolves #688
Resolves #681
Resolves #679
Resolves #671
Resolves #662
Resolves #660
Resolves #659
Resolves #655
Resolves #654
Resolves #653
Resolves #652
Resolves #651
Resolves #647

Motivation and Context

It solves all problems.

How Has This Been Tested?

Unit tests still pass (except the vfg one, but that has been fixed in the other PR)

Screenshots (if appropriate):

image

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

Go over all the following points, and put an x in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTION document.
  • I have updated the CHANGELOG file accordingly for the version that this merge modifies.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@@ -15,24 +15,34 @@ function Get-RubrikVolumeGroup
.LINK
https://rubrik.gitbook.io/rubrik-sdk-for-powershell/command-documentation/reference/get-rubrikvolumegroup

.EXAMPLE
Get-RubrikVolumeGroup -Name 'Quokka volumes'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👀


.EXAMPLE
$currentreport = Get-RubrikReport -name BoringReportName -DetailedObject
$currentreport.name = "Jaap's QuokkaReport"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👀 👀

.EXAMPLE
Get-RubrikReport -Name 'Boring Report' -DetailedObject | Set-RubrikReport -NewName 'Quokka Report'

This will rename the report named 'Boring Report' to 'Quokka Report'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👀 👀 👀

@shamsway shamsway self-requested a review September 11, 2020 01:48
Copy link
Contributor

@shamsway shamsway left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Most impressive

@shamsway shamsway merged commit 3d0cd1e into devel Sep 11, 2020
@shamsway shamsway deleted the jaap-otherissues branch September 11, 2020 01:49
@sujanrubrik
Copy link

@jaapbrasser @shamsway
Have all these commands been fixed now. Some customers use these commands to do backup and restore. And this is impacting their backup and restore operations. Can we have these commands fixed asap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment