@mjwestgate report us that our gbif-es name-matching services was using the ALA name index. I discovered that this was caused by an unattended upgrade of the debian package.
This causes:
to use the ALA default configured name index (not the provided by ala-install)
We have to find a way to not overwrite configs. A good option is to do what we do in pipelines: we use a default la-pipelines.yml config (maintained by the deb package and the pipelines code base) and a la-pipelines-local.yml installed by ala-install and configurable via ansible.
@mjwestgate report us that our gbif-es name-matching services was using the ALA name index. I discovered that this was caused by an unattended upgrade of the debian package.
This causes:
ala-install)We have to find a way to not overwrite configs. A good option is to do what we do in pipelines: we use a default
la-pipelines.ymlconfig (maintained by the deb package and the pipelines code base) and ala-pipelines-local.ymlinstalled byala-installand configurable via ansible.