Since the latest versions, ZOE automatically creates a zapp.yaml file with a default configuration when this file does not exist in the workspace.
We would like to be able to define a customized default zapp.yaml file by ourselves because to date it is always the same zapp.yaml file which is used in all our configurations.
To do this, ZOE would need to manage a “Custom default Zapp file location” setting.
Then we need a way to feed this setting:
manually (on instructions given to users)
by script: we have developed an extension which is already capable of modifying user settings, (we already do this to feed the path parameter to the Java runtime).
Ideally, if the default customized zapp.yaml file was carried by a private extension, (to be able to be deployed and updated), and not be obliged to develop the settings modification script, it would be necessary to be able to give the path to the private extension by means of variables, and in a generic form (a regex) to avoid the problem of numbering of the versions of the private extension.
See also the possibility of giving an http, ssh, or git url, to download the default zapp.yaml customized file.
Use a protocol prefix for customized default zapp file location ? (file://, http[s]://, ssh:// git://, ...).
Description of the enhancement requested
Since the latest versions, ZOE automatically creates a zapp.yaml file with a default configuration when this file does not exist in the workspace.
We would like to be able to define a customized default zapp.yaml file by ourselves because to date it is always the same zapp.yaml file which is used in all our configurations. To do this, ZOE would need to manage a “Custom default Zapp file location” setting.
Then we need a way to feed this setting:
Ideally, if the default customized zapp.yaml file was carried by a private extension, (to be able to be deployed and updated), and not be obliged to develop the settings modification script, it would be necessary to be able to give the path to the private extension by means of variables, and in a generic form (a regex) to avoid the problem of numbering of the versions of the private extension. See also the possibility of giving an http, ssh, or git url, to download the default zapp.yaml customized file. Use a protocol prefix for customized default zapp file location ? (file://, http[s]://, ssh:// git://, ...).
Thanks.