Solved
AEM cloud, how to deploy secret client settings without putting them in GIT?
The standard way to add env. specific config settings is to use OSGi config files and the editor. The problem is that the editor is disabled for Cloud. If we put secrets in git, any developer can access production systems.
how can we get round this? Is there a standard out of the box way to include env specific values which are not in Git, which the backend devs can use for integrating with banking systems etc?
This page:
Says this:
When to use secret environment-specific configuration values
Adobe Experience Manager as a Cloud Service requires the use of environment-specific configurations ($[secret:SECRET_VAR_NAME]) for any secret OSGi configuration values, such as passwords, private API keys, or any other values that cannot be stored in Git for security reasons.
Use secret environment-specific configurations to store the value for secrets on all Adobe Experience Manager as a Cloud Service environments, including Stage and Production.
So there appears to be a mechanism, but there is no mention of how this mechanism works or is used. how do we set the values?