-
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
APIML optimized configuration workflow for V2 #4143
base: v2.x/staging
Are you sure you want to change the base?
Conversation
Signed-off-by: Pavel Zlatnik <[email protected]>
Signed-off-by: Pavel Zlatnik <[email protected]>
Signed-off-by: Pavel Zlatnik <[email protected]>
Signed-off-by: Pavel Zlatnik <[email protected]>
Signed-off-by: Pavel Zlatnik <[email protected]>
Signed-off-by: Pavel Zlatnik <[email protected]>
Signed-off-by: Pavel Zlatnik <[email protected]>
Signed-off-by: Pavel Zlatnik <[email protected]>
Signed-off-by: Pavel Zlatnik <[email protected]>
build 6784 SUCCEEDED. |
Test workflow 5970 is started. |
build 6785 SUCCEEDED. |
Test workflow 5971 is started. |
build 6785 SUCCEEDED. |
Test workflow 5985 is started. |
build 6866 SUCCEEDED. |
@pavelzlatnik do we need to copy the changes in #4154 to this pr? |
Test workflow 6032 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
Changes proposed in this PR
New workflow (based on ZWECONF for zowe v2) developed for simplified and optimized configuration of APIML.
This workflow has fewer steps than full zowe configuration workflow, but is still backward compatible with full zowe (in yaml).
All ports are set in single step, components are preset with aim to APIML best practices.
User has now 2 options, use either zowe configuration workflow (ZWECONF), or in aim for APIML this simplified workflow.
After discussion and agreement with APIML team, this APIML configuration workflow should go already to 2.x
Workflow structure
variables step
ports step
Does this PR introduce a breaking change?
Does this PR do something the person installing Zowe should know about?
We would prepare new documentation section together with Andrew Jandacek. This is optional workflow which could be used instead of ZWECONF workflow during zowe configuration.
multi-line description
Is there a related doc issue or Pull Request?
Doc issue/PR number:
Other information