The first feature is is currently done in the Docker images so should be uncontroversial. As for the others? Using YAML for OMERO.web configuration is a lot easier than a single line of dense JSON, but it's a new feature.
- Read config properties from
CONFIG_omero.... environment variables.
- Read configuration from YAML/JSON: Years ago someone asked whether you could configure something like Mapr from the IDR's ansible configuration variables. Now you almost can with a bit of editting.
- Convert Jinja2 to YAML/JSON: Many of the IDR Ansible variables contain Jinja2 statements. If they are of the form
{{ variable | default('x') }} this can be handled by Jinja2 since default is a built-in filter. This gets us even closer to being able to use the ansible configuration with few changes.
The first feature is is currently done in the Docker images so should be uncontroversial. As for the others? Using YAML for OMERO.web configuration is a lot easier than a single line of dense JSON, but it's a new feature.
CONFIG_omero....environment variables.{{ variable | default('x') }}this can be handled by Jinja2 sincedefaultis a built-in filter. This gets us even closer to being able to use the ansible configuration with few changes.