[Enhancement] Centralized configuration files

[jbyibm]

Today we have multiple configuration files:

• https://github.com/IBM/Bank-of-Z/blob/main/.setup/config/config.yaml (General for Bank of Z installation/update)
• https://github.com/IBM/Bank-of-Z/blob/main/.setup/build/datasets.yaml (DBB datasets)
• https://github.com/IBM/Bank-of-Z/blob/main/dbb-app.yaml (DBB app config - some tools location)
• https://github.com/IBM/Bank-of-Z/blob/main/.setup/deploy/Development.yml (Wazi Deploy environment file)
• https://github.com/IBM/Bank-of-Z/blob/main/.setup/zconfig/bank-of-z-definitions.yaml (CICS Resource Builder, ..)
• ...

We need to consolidate this.

[davidjwriter]

I'll have to look into it more, but I think DBB specifically needs the dbb-app.yaml file and I'm not sure what would happen if we combined the datasets.yaml with other files as DBB will read it all in?

[jbyibm]

We can't change the behavior of the existing tools. We can open ideas for enhancement if needed. But we can "generate" the needed files. For example:

• Add to our config.yml a section for builds that have the datasets.yml content and dump it before the DBB build.
• Do the same for Wazi Deploy.
• We can build a simple Python script for this and use jinja2 for variable resolutions. And also use ${MY_ENV_VAR} in replace it with an environment variable.

@dennis-behm, @MikeFultonDev what do you think? Any other ideas?

[dennis-behm]

It's a fact that the tools configurations reference runtime libraries in different ways. Which is similar to a JCL, and members on the proclib as well.

I would rather suggest that we create proper documentation about necessary configuration of tools (such as compiler location, runtime etc.).