When it's time to build AMQ Streams components in PNC, the component owners use the PNC UI in order to update the build script, alignment parameters or any other build configuration. When a temporary (or persistent) build is ready, the last step is to copy/paste such configuration to the CPaaS build-config YAML for the corresponding pipeline. The copy/paste process can be error prone and we should avoid that.

Other than this, if the component owner is splitting alignment parameters on more lines and then report all of them into the YAML, when the pipeline runs, the bacon CLI pushing the configuration is going to set all the alignment parameters on one line, so even if they are the same a new build starts (because of a configuration change) even if not necessary.

We should investigate a good way to avoid this kind of problems. Several ideas:

• component owners avoid to use the PNC UI but more the bacon CLI to get and or update the PNC configuration so that it always matches with what is generate from the YAML during the pipeline run (because it's using bacon CLI as well).
• adding a safety check in the pipeline which could get all components configurations via bacon CLI and check they are the same in the YAML otherwise failing early.

Details about Bacon here https://project-ncl.github.io/bacon/