Cloud Pak Configuration as Code

We have 3 Installations of Cloud Pak for Data (Stages - PROD, QA, BUILD) and would need the ability to configure the hole instance in a git repository. To Configure Cloud Pak for Data "ArgoCD" like as code in yaml form.

Why do we need this:

• It is extremly time consuming to change the configuratin of one or more Cloud Pak Instances in the UI

• It is not possible or can be only done with huge timely effort and is intransparent to track changes in one environment and in my opinion impossible to compare configurations over the stages. No central place for audit changes.

• If I crash an Instance I don't have a configuration backup - in case of desaster I have to recreate the instance from scratch. Highly time consuming.

What we want:

• I would like to have a git ops repo for Cloud Pak For Data

  • I would like to connect the main branch with the PROD environment (using the production folder)

  • I would like to connect the develop branch with the QA environment (using the qa folder)

  • I would like to connect the develop branch with the BUILD environment (using the build folder)

  • In this form additional instances could be added easily

• We would like to have this workflow

  • Changes can be only done on the develop branch

  • To change something in production we would need to do a pull request to the main branch

• How It should work

  • Changes in the repo should be immediately reflected in Cloud Pak for Data . Like ArgoCD does it.

  • The configuration should be done in yaml format

• In first place we would like to have this for the environment (system setup) in second place for every project. Here we will work with the API for the moment... but this should not be the end scenario.