-
Notifications
You must be signed in to change notification settings - Fork 378
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
Selector in VolumeGroupSnapshotSource API should be optional #995
Selector in VolumeGroupSnapshotSource API should be optional #995
Conversation
6a5e8f1
to
1d6126c
Compare
/cc xing-yang RaunakShah Please have a look, combined with #837 the VolumeGroupSnapshot feature should be pretty much ready for users to try out. |
1d6126c
to
e16739e
Compare
e16739e
to
153a0e7
Compare
153a0e7
to
9e58d4c
Compare
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.
Thanks for catching this!
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nixpanic, RaunakShah, xing-yang The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind api-change
What this PR does / why we need it:
When using a VolumeGroupSnapshotContent for a pre-preprovisioned VolumeGroupSnapshotSource, there is no correct value for the
selector
property. However, the original API requires theselector
to be set, even though it is not used.Which issue(s) this PR fixes:
This problem was identified in #837.
Special notes for your reviewer:
Does this PR introduce a user-facing change?: