-
Notifications
You must be signed in to change notification settings - Fork 51
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
Read yaml by configmgr - zwe init
#4088
base: v3.x/staging
Are you sure you want to change the base?
Conversation
Signed-off-by: Martin Zeithaml <[email protected]>
Signed-off-by: Martin Zeithaml <[email protected]>
build 6434 SUCCEEDED. |
build 6435 SUCCEEDED. |
Test workflow 5685 is started. |
Test workflow 5686 is started. |
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.
this fails due to different behavior of configmgr:
- read_yaml_configmgr process /zowe/inst/no-nodeinit/zowe.yaml and extract '.zowe.setup.certificate.keyring.zOSMF.user -> /zowe/setup/certificate/keyring/zOSMF/user'
* Exit code: 0
* Output:
error not found, reason=101
...
* certificate pkcs12 import --keystore /zowe/inst/no-nodeinit/keystore/error not found, reason=101/error not found, reason=101.keystore.p12 --password error not found, reason=101 --alias error not found, reason=101 --source-keystore error not found, reason=101 --source-password error not found, reason=101 --source-alias error not found, reason=101
looks like errors need to be >/dev/null
It seems to be more complicated, the error in printed to stdout and return code is always 0 (found/not found). I am afraid, the only shell solution for now is to check if the return value is The right solution would be update configmgr to return > 0 for "not found" case. |
Signed-off-by: Martin Zeithaml <[email protected]>
build 6441 SUCCEEDED. |
Test workflow 5691 is started. |
Continuation of #4069.
Simple NodeJS dependency removal for
zwe init
command while waiting for #3718.