Our company is using Splunk Entreprise 8.2.9 with application configuration/retention in GitLab.
We have few concerns when it comes to add-ons configuration and Apps configuration that store credentials (username/passwords) in their files (inputs.ini or password.conf)
As of now we are using the Web UI to locally configure the addons that will store the configurated credentials in the local directory of the addon in a password.conf file showing ******* for the credentials.
The problem of such scenario is when it comes to add-on upgrade the credential file is not read and we have to start again the configuration of the addon.
In order to avoid such time waste we'd like to store in a dedicated app the configuration of the addon or to have the needed credentials stored in Apps. Main concern is all our Splunk configuration is stored in GitLab. To avoid data breach we have to encrypt those creds. Is it possible to store encrypted values for credentials in GitLab that Splunk will be able to read easily for example by using pass4symkey or salt ? Or any other encrypted method