You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 18, 2021. It is now read-only.
Configuration changes made in Ansible do not seem to be propagated to an installed server. I installed a test server with training-server.yml, and afterwards set
---
omero_dbpassword: "kukkuu"
and ran the playbook again. The change shows up in a config file, but not in "omero config"
(omego)[omero@omero ~]$ cat config/omero-base.config
config set omero.db.host localhost
config set omero.db.user omero
config set omero.db.name omero
config set omero.db.pass kukkuu
config set omero.data.dir /OMERO
# Additional custom options
(omego)[omero@omero ~]$ omero config list
omero.data.dir=/OMERO
omero.db.host=localhost
omero.db.name=omero
omero.db.pass=omero
omero.db.user=omero
Looking at roles/omero-server/tasks/main.yml, it seems that only omego install and omego upgrade use this configuration. Maybe there could also be a handler to run omero config set when omero-base.config or omero-additional.config are changed?
Configuration changes made in Ansible do not seem to be propagated to an installed server. I installed a test server with training-server.yml, and afterwards set
and ran the playbook again. The change shows up in a config file, but not in "omero config"
Looking at
roles/omero-server/tasks/main.yml, it seems that onlyomego installandomego upgradeuse this configuration. Maybe there could also be a handler to runomero config setwhenomero-base.configoromero-additional.configare changed?