This adds example entries for `DCR_SYNC_LOGIN_ENDPOINT` and `DCR_SECRET_KEY`
environment settings for the worship consumers. The example value for
`DCR_SYNC_LOGIN_ENDPOINT` was chosen to match the value for `DCR_SYNC_BASE_URL`.
The consumer needs to dispatch data to two different graphs: the worship
services graph and the privacy graph, based on triple type and/or
property. The latest version of the consumer doesn't allow it to be done
in one consumer instance, hence de split into two consumers.
OP will take over the editing of contact data again. This removes the CLB
consumer from OP altogether such that it cannot be accidentally be reactivated.
Re-enable editing contact data in OP as the CLB app editing functionality was
disable due to data flow issues. This sets the relevant frontend feature flag
such that it allows editing the contact data for all organizations
classifications agains.
When deploying make sure this environment variable is **not** overwritten in the
environment's `docker-compose.override.yml`.
This service will be used to insert and delete triples for the
`org:hasSubOrganization` and `org:linkedTo` predicates when appropriated
memberships have been added or deleted to the triplestore.
A new bug fix release was made for the
`construct-organization-relationships-service`. This release is fully backward
compatible and requires no further changes.
There was an issue with the old producers not taking into account all
graph filters, thereby exporting sometimes too many triples.
Note: please consider moving these old producers to the latest
one. (It should be a matter of shuffling config around)
