-
Notifications
You must be signed in to change notification settings - Fork 54
🌱 Revert v1a3 vm.status.storage.usage to 9.x #930
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
Open
akutz
wants to merge
1
commit into
vmware-tanzu:main
Choose a base branch
from
akutz:feature/change-v1a3-vm-status-storage
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
🌱 Revert v1a3 vm.status.storage.usage to 9.x #930
akutz
wants to merge
1
commit into
vmware-tanzu:main
from
akutz:feature/change-v1a3-vm-status-storage
Conversation
This file contains hidden or 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
This patch updates the VM API status.storage.usage data structure to be what it used to be, and what it shipped as in vC 9.0. The intent was to ship vC 9.0 with the same status.storage.usage structure now seen in v1alpha4, but there were some reverts, and those changes were discarded.
Minimum allowed line rate is |
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.
What does this PR do, and why is it needed?
This patch updates the VM API status.storage.usage data structure to be what it used to be, and what it shipped as in vC 9.0.
The intent was to ship vC 9.0 with the same status.storage.usage structure now seen in v1alpha4, but there were some reverts, and those changes were discarded.
Which issue(s) is/are addressed by this PR? (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes
NA
Are there any special notes for your reviewer:
Please add a release note if necessary: