6940_April_2_SafKeyringConfigSlashes #4277
Open
Conversation
This file contains 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
The following is mentioned: While migrating from Zowe v2.18, if you are using keyrings, verify that Zowe YAML references to `safkeyring` use 2 slashes, not 4, such as `safkeyring://` instead of `safkeyring:////`
ArooshLele
added
area: docs
ArooshLele
requested review from
DivergentEuropeans,
struga0258,
1000TurquoisePogs,
janan07 and
anaxceron
|
😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.
Need help? Contact the Doc Squad in the #zowe-doc Slack channel. |
1 similar comment
|
😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.
Need help? Contact the Doc Squad in the #zowe-doc Slack channel. |
anaxceron
reviewed
Apr 2, 2025
| @@ -34,6 +34,7 @@ To migrate from Zowe **v2.16.0** or a lower version, perform the following tasks | |||
|
|
|||
| 2) Update your PROCLIB entries for Zowe, as enhancements and default parameters have changed throughout Zowe v2. | |||
| This can be performed with the unix command `zwe init stc`, by running the job ZWEISTC, or by copying the SZWESAMP members ZWESLSTC, ZWESISTC, and ZWESASTC into your desired PROCLIB. | |||
| 3) If you are using keyrings, verify that Zowe YAML references to `safkeyring` use 2 slashes, not 4, such as `safkeyring://` instead of `safkeyring:////`. | |||
There was a problem hiding this comment.
We should spell out 2 and 4. Typically, single-digit numbers are spelled out (when not used in measurements).
There was a problem hiding this comment.
That sentence was taken from the same article, it should be identical on both places.
| @@ -28,6 +28,8 @@ System demos are typically held the week after a minor release becomes available | |||
|
|
|||
| * It is now possibile to use custom logback.xml in all API ML services. Configuration for separate services can be performed by adding logging.config parameter under each API ML component in Zowe YAML file. ([#3669](https://github.com/zowe/api-layer/issues/3669)) | |||
|
|
|||
| * While migrating from Zowe v2.18, if you are using keyrings, verify that Zowe YAML references to `safkeyring` use 2 slashes, not 4, such as `safkeyring://` instead of `safkeyring:////`. | |||
There was a problem hiding this comment.
- We should spell out 2 and 4. Typically, single-digit numbers are spelled out (when not used in measurements).
- To tighten up this sentence, I would include the examples in parentheses after the slash counts: " ... use two forward slashes (
safkeyring://), not four (safkeyring:////).
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.
Describe your pull request here:
The following is mentioned:
While migrating from Zowe v2.18, if you are using keyrings, verify that Zowe YAML references to
safkeyringuse 2 slashes, not 4, such assafkeyring://instead ofsafkeyring:////List the file(s) included in this PR:
After creating the PR, follow the instructions in the comments.