Because the role is internally patching the NGINX configuration created by the ome.omero_web role, a possible issue is that executing the idr-omero-web.yml playbook in isolation can revert this change. This is effectively what happened in https://github.com/IDR/deployment/pull/435 in order to deploy an OMERO.map configuration change
There are a few possible options to make the systems more robust:
either consider the sub-playbooks should no longer be executed individually and only idr-01-install-idr.yml should be executed when modifying a deployment. An advantage of this approach is that it should ensure that all playbooks are run in the order. A downside is the execution time. In particular, tackling https://github.com/IDR/deployment/issues/433 might be useful if this is the approach
move the ome.omero_ms_image_region role to the idr-omero-web.yml playbook so that it can always be executed after the ome.omero_web role and prevent any regression in the NGINX configuration
The deployment of the image-region micro-service was added in https://github.com/IDR/deployment/pull/430 via the extension the
idr-omero-readonly.ymlplaybook.Because the role is internally patching the NGINX configuration created by the
ome.omero_webrole, a possible issue is that executing theidr-omero-web.ymlplaybook in isolation can revert this change. This is effectively what happened in https://github.com/IDR/deployment/pull/435 in order to deploy an OMERO.map configuration changeThere are a few possible options to make the systems more robust:
idr-01-install-idr.ymlshould be executed when modifying a deployment. An advantage of this approach is that it should ensure that all playbooks are run in the order. A downside is the execution time. In particular, tackling https://github.com/IDR/deployment/issues/433 might be useful if this is the approachome.omero_ms_image_regionrole to theidr-omero-web.ymlplaybook so that it can always be executed after theome.omero_webrole and prevent any regression in the NGINX configuration/cc @dominikl