-
Notifications
You must be signed in to change notification settings - Fork 5
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
feat: LMGR-656: Creating lpar failed due to cryptoConfigration field … #13
Conversation
…in request body Signed-off-by: zhangli <[email protected]>
zhangli@bogon golang-zhmcclient % bash go-test.sh -p pkg/zhmcclient |
Now in golang-zhmcclient, the struct using for request body of creating lpar and getting lpar is the same, to fix this issue https://jsw.ibm.com/browse/ZLPARAAS-1455, baremetal team make cryptoConfiguration field ignored when doing unmarshal. But for getting lpar properties, we need this field. Since content of request body of creating lpar and result of getting lpar is different, i define a new struct for result of getting lpar to avoid issue in https://jsw.ibm.com/browse/ZLPARAAS-1455, |
@huoqifeng @jiangphcn please help review. |
LGTM - i assume that we can't directly change the |
@jiangphcn |
@bjzhangl there are several place which refer |
@huoqifeng i only know zvpcmanager use it. Baremetal may use it, but baremetal has been offline. Do you know other place that use it? |
I think other consumers should not be a problem because the change will be in a new |
@huoqifeng i have pasted the unit test result in the first comment and change the related parts. You can review the code. |
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.
LGTM
…in request body