ACE integration runtime configuration object for ACE Vault

Since a few years we have been running ACE on CP4I on Openshift.

We do not use the mqsicredentials object for ACE credentials since it slows down the ACE integration runtime/server startup (we have one big file per environment) and if the developer makes a mistake in one of the credentials, the pod startup fails, if there is a cluster restart (such as an Openshift upgrade) all ACE pods would fail which causes business downtime.

Therefore we are using the ACE integration runtime "generic" configuration object to mount the ACE Vault (with a simlink ofcourse) as a workaround: the mqsicredentials commands are run on a "unique ACE pod" using GNU Parallel to speed up the execution, the result of which is ACE Vault zipped and ready to be mounted onto an ACE integration runtime pod. We also have a webhook on the Openshift secret that holds the mqsicredentials commands so that when user updates the secret, the "unique ACE pod" would trigger a fresh addition of credentials into a pre-build Vault. It works very well and the pod startup is instant as the Vault is initialized on startup with the vault-key passed as an environment variable, but it would be the ideal solution if you'd offer this functionality as part of the ACE configuration object.

How it should work: The ACE credentials file consisting of all the mqsicredentials commands would be added to the ACE configuration object called "aceVault" which would construct an ACE vault and then execute the mqsicredentials commands and create an Openshift secret holding the ACE Vault file ready to be mounted onto the ACE integration runtime pods.

Official documentation: https://www.ibm.com/docs/en/app-connect/containers_cd?topic=resources-configuration-reference