One of our customers wants to have an automated deployment (their security department is forcing this requirement by the way) were a single WAR file is provided to the release manager containing the code (valid for all the environments) and then a configuration file with the properties for each environment out of the war and managed and accesible only per each environment
Is that feasible in the current CUBA application?
As far as we know the only way we have now is to generate a different war file with the properties inside per each environment.
They don’t want this as they need to manage different war versions.
the only way we have now is to generate a different war file with the properties inside per each environment.
That’s not true.
You can specify environment-specific properties in local.app.properties files.
Note that if you are using single WAR then location of these files is determined in the single-war-web.xml, in the appPropertiesConfig context parameter. There can be two files: one for web module and one for core module.