Configuration Management/Deployment (DBCs) for MAS SaaS

This request is based on some discussions with the SRE team related to how configuration management for large Maximo implementations in MAS SaaS can be improved and automated, leveraging the same way extensions are done in the system (i.e.: via DBCs).

In conversations with the SRE team, it has been highlighted that there's no out-of-the-box mechanism available to allow IBMC or any project team to promote configuration changes via DBCs and although Migration Manager is the recommended option, it does not provide the benefits that DBCs do and how an usual large implementation project works with teams working on local instances and promoting changes to a code repository tool that can trigger and manage deployments automatically and effectively to higher environments.

Currently, the SRE team is able to take zip files created by project teams, but the process is very manual and relies on files being uploaded to Box folders or transmitted via FTP with some security risks. From there, a ticket has to be raised for the SRE team to perform more manual steps on OpenShift and trigger the build/deployment. It would be great if APIs could be made available to allow steps to be automated or if COS bucket(s) could be leveraged once a build file is made available by the project team, eliminating the manual steps and allowing deployments to happen more regularly.