sensitive-data-service.yml issues

[adam-collins]

Failed to run sensitive-data-service.yml on a new server.

Issues found

• cannot override namematching-service version. The default version (latest) fails. Success with ala_namematching_service_version=1.8-SNAPSHOT+0~20220601053108.49~1.gbp224ac7
• need directory /var/log/atlas
• need directory /var/log/atlas/sensitive-data-service/ as user sds-data
• edit /data/ala-sensitive-data-service/config/config.yml for the installed Lucene directory /data/lucene/namematching-sd
• edit /etc/systemd/system/multi-user.target.wants/ala-namematching-service.service for java arm64 instead of amd64
• edit /etc/systemd/system/multi-user.target.wants/ala-sensitive-data-service.service for java arm64 instead of amd64
• ran it with deployment_type=vm in the inventory

[adam-collins]

Can anyone explain to me why sensitive-data-service requires namematching-service installed? I cannot find how https://github.com/AtlasOfLivingAustralia/ala-sensitive-data-service uses https://github.com/AtlasOfLivingAustralia/ala-namematching-service.