The version property has been deprecated for a while. Now that the servers are
on a recent version of docker compose these can be removed from our
configurations. This avoids that the warnings are shown each time.
Considering the time it takes to do a full re-index the speed benefit of the
development-specific configuration is limited. To the point that it does not
seem to outweigh the added complexity of maintaining two configurations and the
added chance of errors that brings.
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.
The most recent merge commit from master to branch contained error were a
removed line was reinserted at a wrong place with an incorrect indentation .his
causes (some) drc commands to fail with an error
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.
* Set up deltas for sync with sharepoint
* add service
* add dev environment variables
* Extract config to the stack
* Adjust the config and mappings
* Filter out worship services
* Add contacten sp list service
* Add configuration for contact list
* Add config files for contacten sync
* Wire sharepoint sync on main graph instead of producer
* Add env variables
* Add op sync initiator
* Minor updates
* Improve config, add job controller rules and more
* Adjust rules
* Remove unused producer changes
* Don't restart initiator on dev setup
* Sync OP status to a dedicated column
* Add ABB_ID and split bus and house numbers
* Remove config file we will not use
* Add NIS and secondary phone number, rename columns
* Remove isInitialMatchingMapping, not used anymore
* Match on URI instead of UUID
* Adapt field names to new lists
* Specify matching field in config
* Set version of op-sync-with-sharepoint
---------
Co-authored-by: Nordine Bittich <nordine@bittich.be>
* Add delta rules
* Remove delta rules
We need to use a direct endpoint to trigger the update instead of the
deltas to be able to see in the frontend the direct result of our change
* Add dispatching rule to sync ovo service
* Add released sync-ovo-number service
