-
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
Clean up the code when checking z/OSMF [v2] #3971
Conversation
Signed-off-by: Martin Zeithaml <[email protected]>
build 5892 SUCCEEDED. |
Signed-off-by: Martin Zeithaml <[email protected]>
build 5893 SUCCEEDED. |
build 5951 SUCCEEDED. |
Test workflow 5321 is started. |
Please check if your PR fulfills the following requirements. This is simply a reminder of what we are going to look for before merging your PR. If you don't know all of this information when you create this PR, don't worry. You can edit this template as you're working on it.
PR type
What type of changes does your PR introduce to Zowe? Put an
x
in the box that applies to this PR. If you're unsure about any of them, don't hesitate to ask.Relevant issues
Fixes #3932
Changes proposed in this PR
ZWEL0141E
contains a text$(get_user_id)
instead of real userIDz/OSMF is not configured. Using z/OSMF as authentication provider is not supported.
Does this PR introduce a breaking change?
Testing
Always this setting:
With or without fix, if
discovery.enabled=true
:Successfully checked z/OS MF is available on 'https://example.com:1234/zosmf/info'
But when this is set:
No fix, confusing error message is printed and the zowe continues:
ERROR: z/OSMF is not configured. Using z/OSMF as authentication provider is not supported.
With fix, error with reason is printed and zowe is terminated: