-
Notifications
You must be signed in to change notification settings - Fork 133
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
Updated advanced configuration for app framework page for v3 #3939
Conversation
Signed-off-by: 1000TurquoisePogs <[email protected]>
😺 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. |
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.
Please see the broken links report for broken links introduced in this PR
Signed-off-by: Andrew Jandacek <[email protected]>
Signed-off-by: 1000TurquoisePogs <[email protected]>
I think this PR's content could be ready to go, but I'm just awaiting review from more webui members to see if they have other feedback. |
…this section was removed Signed-off-by: Andrew Jandacek <[email protected]>
The link checker test now passes. |
Broken links have been fixed |
The page "Configuring Zowe Application Framework" (mvd-configuration.md) is currently accurate for v3, but just overall dated.
There are things in here that don't need to be said for v3, or can be said more simply because documentation elsewhere has been created and refined (AT-TLS documentation, MFA, how to access)
There are things here (v1 environment variable compatibility and HTTP mode) that I do not want documented because there is no reason why anyone should do that these days.
And finally, the name in the sidebar and the similar APIML page do not match a naming scheme.
I have updated this page's title to match APIML's so that there is some consistency.