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

Properly extract CPU speed in VCH creation handler #6611

Merged
merged 1 commit into from
Oct 24, 2017

Conversation

zjs
Copy link
Member

@zjs zjs commented Oct 23, 2017

Because JSON and Go have different models for inheritance, properly interpreting the structure of the API parameters can be confusing.

In this case, we need to reference the nested units variable from the "subclass" instead of the units variable in the parent, which will always have its zero value (the empty string).

Note that this was discovered while working on #6019 and will be tested as a part of #6527.

Because JSON and Go have different models for inheritance, properly
interpreting the structure of the API parameters can be confusing.

In this case, we need to reference the nested units variable from
the "subclass" instead of the units variable in the parent, which
will always have its zero value (the empty string).
@zjs zjs added area/api The Vritual Container Host management API component/install kind/defect Behavior that is inconsistent with what's intended priority/p2 team/lifecycle labels Oct 23, 2017
@zjs zjs added this to the Sprint 19 Lifecycle milestone Oct 23, 2017
@zjs zjs self-assigned this Oct 23, 2017
@zjs zjs requested review from jzt and AngieCris October 23, 2017 23:48
Copy link
Contributor

@mdharamadas1 mdharamadas1 left a comment

Choose a reason for hiding this comment

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

lgtm

@zjs zjs merged commit 425b706 into vmware:feature/vic-machine-service Oct 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api The Vritual Container Host management API cla-not-required component/install kind/defect Behavior that is inconsistent with what's intended priority/p2 team/lifecycle
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants