Create simplified alternative automated solution (Watsonx?) for managing database credentials in agent configuration.yaml file in large dynamic environments.

>During Adobe Instana POC customer provided feedback that the Instana agent configuration that is specific to Adobe's environment seems complex, time consuming, and cumbersome:

Create simplified alternative automated solution for managing database credentials in agent configuration.yaml file in large dynamic environments.

Perhaps using WatsonX might be a way to greatly simplify it.

-Adobe auto provisions dbaas, nwaas, lbaas, hostaas,  via cyberarc, teleport, and salt workflows, then auto destroy it after a set time, or may only destroy part of it if it is an application

-Trying to install and manage the Instana Agent .yaml configration manually would be very time consuming

-Their Oracle DB environment is highly dynamic, they may have 20 Oracle RAC Clusters with 10 DBs each, and some may only be provision for 1 week, 1 day or a few hours

-Adobe also has strict password policies that require distinct, unique passwords, and also enforce frequent password expiration policies that may require DBs to change the passwords weekly

-Instana requires DB Credentials for EACH DB, and updating Oracle DB credentials for each DB in the configuration.yaml file and would be very labor intensive to manage

>To address this, we previously recommend exploring integrating Instana into their configuration management tool—such as Ansible to automate synchronization and updates to the install agent’s configuration file, which would help ensure that whenever a new database is created, decommissioned, or has its password changed, the configuration file is automatically updated.

-Adobe's feedback was yes this is feasible, but Instana is limited in the number of tools it currently integrates with (mainly Ansible), they have salt, cyberarc, and teleport none of which are supported by Instana.

-Adobe also provided feedback that it would be a better solution to natively automate this type of configuration management into Instana, or at least increase the number of configuration management tools that Instana can integrate with. 

>The customer also commented on how burdensome in general managing the configuration.yaml would be in a application heavy environment that requires significant

Tweaking of potential hundreds of configuration.yaml files.  So is there a better, more creative way that IBM can manage configuration.yaml in general? (WatsonX?)