-
Notifications
You must be signed in to change notification settings - Fork 22
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
[minor] Optional Watson Studio bind to Health #418
Conversation
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.
image/cli/install-ansible/ibm-mas_devops.tar.gz needs to be removed
This item has already been addressed (zip file was removed)
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.
LGTM
As devops has been merged: ibm-mas/ansible-devops#979 I will merge this 👍 |
PRs:
Please refer to CLI PR for a complete description of the new binding requested by Health team.
About optional studio binding
This PR allows users to optionally bind Watson Studion with Health (in ManageWorkspace CR)
In order to do that a new parameter has been added in PIpeline:
By default, it is
false
, but can be set astrue
, indicating CPD and Studio must be provisioned and bound to ManageMAS_APPWS_BINDINGS_HEALTH_WSL_FLAG
will be set astrue
and so will be informed in PipelineRunWhen install or install-with-fvt pipelines are parameterized with
mas_appws_bindings_health_wsl
=system
, three tasks will be enabled.... as they had their
when
criteria modified accordingly:suite-app-config
task will then receive this new parameter and based on that will modify ManageWorkspace CR bindings and, besides jdbc, will include studio as defined hereTest Evidences:
In CLI
In FVT