Updated add province uri migration to avoid duplicates Added a cleanup migration for adding province URIs to addresses Updated the export,json config to expose the province URI of addresses Fixing errors after review Updated CHANGELOG Refactored and corrected migrations, changed the timestamps refactoring cleanup migrations Refactored the cleanup add province migrations Updated changelog to ensure db-cleanup-service picks up the new jobs.
17 KiB
Changelog
Unreleased
Backend
- Fix KBO statuses not being displayed [OP-3584]
- datafix: update NIS2019 end dates and link additional NIS2025 to werkingsgebieden [part of OP-3566]
- datafix: correct date of change event of ckb olen [OP-3594]
- datafix: move memberships from shared to administrative unit graph
- datafix: cleanup werkingsgbieden data [OP-3566]
- Move werkingsgebieden to public graph
- Link district werkingsgebieden to Antwerp municipality werkingsgebied
- Add missing werkingsgebied for Borsbeek district
- Write migration to extract from existing primary sites the province URI [OP-3597]
Deploy Notes
drc restart migrations; drc logs -ft --tail=200 migrations
drc up -d kbo-data-sync
drc exec kbo-data-sync curl -X POST http://localhost/sync-all-kbo-data
drc restart delta-producer-publication-graph-maintainer
drc exec delta-producer-background-jobs-initiator curl -X POST http://localhost/public/healing-jobs # or wait until nightly healing kicks in
drc exec delta-producer-background-jobs-initiator curl -X POST http://localhost/organizations/healing-jobs # or wait until nightly healing kicks in
drc exec db-cleanup curl -X POST "http://localhost/cleanup"
v1.31.2 (2025-04-02)
Backend
- Extend the public producer to include: [CLBV-980]
- NIS codes
- Sites and statuses of representative organs
- Secondary sites with their contacts and addresses
- Site descriptions
Deploy notes
drc restart delta-producer-publication-graph-maintainer
v1.31.1 (2025-04-01)
Backend
- Removal of change events of 8 ckb's + update of their status [OP-3562]
Deploy Notes
drc restart migrations-triggering-indexing; drc logs -ft --tail=200 migrations-triggering-indexing
drc restart migrations; drc logs -ft --tail=200 migrations
v1.31.0 (2025-03-27)
Frontend
- Bump to version v1.30.0
Backend
- Datafix: move status for municipalities and provinces to the
sharedgraph such that it can be read by worship users [OP-3469] - Bump
triplestoreandpublication-triplestoretov1.3.0-rc.1. [OP-2492] [OP-3547] - Add missing docker compose keys. [DL-6490]
- Reorganize delta consumers config to harmonize with the ecosystem
- Set up the dashboard app [OP-3103]
- Datafix: correct date of change event of kerkfabriek st petrus [OP-3555]
- Update OCMWv to VVMW [OP-3565] and back. It's technically a nil-operation. But you should run the migrations nevertheless.
Deploy notes
drc restart migrations-triggering-indexing
drc restart migrations; drc logs -ft --tail=200 migrations
drc pull frontend; drc up -d frontend
drc up -d mandatarissen-consumer leidinggevenden-consumer worship-services-main-info-consumer worship-services-private-info-consumer
For upgrade databases
This README provides the necessary steps for upgrading the database. NOTE: This will involve shutting down the app for small period of time (around 30 minutes).
For adding the missing keys
drc up -d search elasticsearch
Dashboard
The dashboard requires some server specific configuration before it can be used.
1. Dashboard domains
To configure the domain name that's used by the dashboard frontend, you can add it to the VIRTUAL_HOST and LETSENCRYPT_HOST environment variables of the identifier service.
- DEV domain: dashboard.dev.app-organisation-portal.contacthub-dev.s.redhost.be
- QA domain: dashboard.qa.app-organisation-portal.contacthub-dev.s.redhost.be
- PROD domain: dashboard.app-organisation-portal.organisaties.s.redpencil.io
2. Dashboard users
Before we can generate a user we need to add an application salt to the server. Add a MU_APPLICATION_SALT environment variable to the dashboard-login service in the docker-compose.override.yml file.
Once this is done you can generate a user by running mu script project-scripts generate-dashboard-login and following the prompts. A new local migration will be generated which can be run by restarting the migrations service and which will insert the new user into the database.
Store the login credentials as a comment in the docker-compose.override.yml file.
3. (Re)start the needed services
drc up -d frontend-dashboard dashboard-login identifier; drc restart dispatcher resource db
v1.30.5 (2025-03-10)
Backend
- Added
http://www.w3.org/ns/prov#Locationto delta stream 'public' [DL-6496]
Deploy notes
drc restart delta-producer-publication-graph-maintainer
drc exec delta-producer-background-jobs-initiator curl -X POST http://localhost/public/healing-jobs
v1.30.6 (2025-03-25)
Backend
- Flushed landingzones [DL-6552]
Deploy notes
drc restart migrations
v1.30.5 (2025-03-10)
Backend
- Added
http://www.w3.org/ns/prov#Locationto delta stream 'public' [DL-6496]
Deploy notes
drc restart delta-producer-publication-graph-maintainer
drc exec delta-producer-background-jobs-initiator curl -X POST http://localhost/public/healing-jobs
v1.30.4 (2025-03-06)
Backend
- Add missing codes to public producer [DL-6210] [DL-6449]
Deploy commands
drc restart migrations delta-producer-publication-graph-maintainer
drc exec delta-producer-background-jobs-initiator curl -X POST http://localhost/public/healing-jobs
v1.30.3 (2025-03-04)
Frontend
- Bump to v1.29.1
Deploy notes
- Bump frontend
Deploy commands
drc pull frontend; drc up -d frontend
v1.30.2 (2025-02-28)
Backend
- Datafix: add new timed governing bodies for new legislature for AGBs [OP-3552]
Deploy notes
- Restart the migration service
- Start a healing job the public producer, or wait for it to kick in overnight
Deploy commands
drc restart migrations; drc logs -ft --tail=200 migrations
drc exec delta-producer-background-jobs-initiator curl -X POST http://localhost/public/healing-jobs
v1.30.1 (2025-02-20)
Backend
- Bestuursorgaanclassificatiecode of VGC was in wrong graph, so it wouldn't export. [DL-6428]
Deploy notes
drc restart migrations
v1.30.0 (2025-02-19)
Frontend
- Bump to version v1.29.0
Backend
- Datafix: delete duplicate identifiers [OP-3157]
- Feature: replace different relations between organisations by memberships [OP-3195 (epic), OP-2606, OP-3156, OP-3198, OP-3199, OP-3258, OP-3259, OP-3260, OP-3265, OP-3293, OP-3305]
- Added
db-cleanup-serviceto keep membership data backwards compatible [OP-3369] - Datafix: delete incorrect change event [OP-3363]
- Feature: re-enable contact data editing [OP-3425]
- Remove gemeente and provincie classifications from admin unit graph [OP-3393]
- Remove several OCMW bcsd faciliteitgemeenten [OP-3535]
- Completely remove AGB Stekene's data. [OP-3409]
- Remove reasoner service, replaced by new consumer logic
Deploy Notes
- Before pulling the changes
- Shut down the reasoner and thank it for its good service:
drc down reasoner
- Shut down the reasoner and thank it for its good service:
- Re-enable contact date editing:
- remove
EMBER_ENABLE_EDIT_CONTACT_DATA_FEATUREflag indocker-compose.override.yml - Stop and remove the
clb-contact-data-consumerservice - Remove the
clb-contact-data-consumerconfiguration indocker-compose.override.yml
- remove
- Rebuild the
searchservice before starting the re-indexing - To enable the membership functionality:
- Restart migration service
- Restart services for which the configuration was changed:
resource,dispatcheranddb - Start the
db-cleanupservice - Pull and restart the frontend
- Perform a re-index using
reset-elastic.shscript
Deploy commands
drc down clb-contact-data-consumer
drc up -d search
drc restart migrations; drc logs -ft --tail=200 migrations
drc restart migrations-triggering-indexing && drc logs -ft --tail=200 migrations-triggering-indexing
drc restart resource dispatcher db
drc up -d db-cleanup
drc pull frontend; drc up -d frontend
./scripts/reset-elastic.sh
1.29.2 (2025-02-17)
Data fix
- restore betrokken lokale besturen that have been accidentally flushed [OP-3546]
1.29.1 (2025-02-14)
Backend
- re-init
worship-services-sensitive-consumer[OP-3483]
Deploy notes
⚠️ Ensure first loket did a full re-sync again of this delta-stream.
drc stop worship-services-main-info-consumer worship-services-private-info-consumer
drc retart migrations
Update docker-compose.override.yml to remove the config of the consumers and replace it by:
worship-services-main-info-consumer:
environment:
DCR_SYNC_BASE_URL: "https://loket.lblod.info" # or another endpoint
DCR_SYNC_LOGIN_ENDPOINT: "https://loket.lblod.info/sync/worship-services-sensitive/login" # or another endpoint
DCR_SECRET_KEY: "key-of-the-producer"
DCR_LANDING_ZONE_DATABASE: "triplestore" # for the initial sync, we go directly to virtuoso
DCR_REMAPPING_DATABASE: "triplestore" # for the initial sync, we go directly to virtuoso
DCR_DISABLE_INITIAL_SYNC: "false"
DCR_DISABLE_DELTA_INGEST: "false"
worship-services-private-info-consumer:
environment:
DCR_SYNC_BASE_URL: "https://loket.lblod.info" # or another endpoint
DCR_SYNC_LOGIN_ENDPOINT: "https://loket.lblod.info/sync/worship-services-sensitive/login" # or another endpoint
DCR_SECRET_KEY: "key-of-the-producer"
DCR_LANDING_ZONE_DATABASE: "triplestore" # for the initial sync, we go directly to virtuoso
DCR_REMAPPING_DATABASE: "triplestore" # for the initial sync, we go directly to virtuoso
DCR_DISABLE_INITIAL_SYNC: "false"
DCR_DISABLE_DELTA_INGEST: "false"
Then
drc up -d db mandatarissen-consumer leidinggevenden-consumer worship-services-main-info-consumer worship-services-private-info-consumer
# Wait until success of the previous step
Then, update docker-compose.override.yml to:
worship-services-main-info-consumer:
environment:
DCR_SYNC_BASE_URL: "https://loket.lblod.info" # or another endpoint
DCR_SYNC_LOGIN_ENDPOINT: "https://loket.lblod.info/sync/worship-services-sensitive/login" # or another endpoint
DCR_SECRET_KEY: "key-of-the-producer"
DCR_LANDING_ZONE_DATABASE: "db"
DCR_REMAPPING_DATABASE: "db"
DCR_DISABLE_DELTA_INGEST: "false"
DCR_DISABLE_INITIAL_SYNC: "false"
worship-services-private-info-consumer:
environment:
DCR_SYNC_BASE_URL: "https://loket.lblod.info" # or another endpoint
DCR_SYNC_LOGIN_ENDPOINT: "https://loket.lblod.info/sync/worship-services-sensitive/login" # or another endpoint
DCR_SECRET_KEY: "key-of-the-producer"
DCR_LANDING_ZONE_DATABASE: "database"
DCR_REMAPPING_DATABASE: "database"
DCR_DISABLE_DELTA_INGEST: "false"
DCR_DISABLE_INITIAL_SYNC: "false"
drc up -d
sh scripts/reset-elastic.sh
1.29.0 (2025-02-07)
Backend
Consumer
- Upgraded
mandatarissen-consumer[OP-3510] - Upgraded
leidinggevenden-consumer[OP-3533], [OP-3511] - Upgraded
worship-services-sensitive-consumer[OP-3337]
Deploy notes
drc down;
Update docker-compose.override.yml to remove the config of the consumers and replace it by:
mandatarissen-consumer:
environment:
DCR_SYNC_BASE_URL: "https://loket.lblod.info" # or another endpoint
DCR_LANDING_ZONE_DATABASE: "triplestore" # for the initial sync, we go directly to virtuoso
DCR_REMAPPING_DATABASE: "triplestore" # for the initial sync, we go directly to virtuoso
DCR_DISABLE_DELTA_INGEST: "false"
DCR_DISABLE_INITIAL_SYNC: "false"
leidinggevenden-consumer:
environment:
DCR_SYNC_BASE_URL: "https://loket.lblod.info" # or another endpoint
DCR_LANDING_ZONE_DATABASE: "triplestore" # for the initial sync, we go directly to virtuoso
DCR_REMAPPING_DATABASE: "triplestore" # for the initial sync, we go directly to virtuoso
DCR_DISABLE_DELTA_INGEST: "false"
DCR_DISABLE_INITIAL_SYNC: "false"
worship-services-main-info-consumer:
environment:
DCR_SYNC_BASE_URL: "https://loket.lblod.info" # or another endpoint
DCR_SYNC_LOGIN_ENDPOINT: "https://loket.lblod.info/sync/worship-services-sensitive/login" # or another endpoint
DCR_SECRET_KEY: "key-of-the-producer"
DCR_LANDING_ZONE_DATABASE: "triplestore" # for the initial sync, we go directly to virtuoso
DCR_REMAPPING_DATABASE: "triplestore" # for the initial sync, we go directly to virtuoso
DCR_DISABLE_INITIAL_SYNC: "false"
DCR_DISABLE_DELTA_INGEST: "false"
worship-services-private-info-consumer:
environment:
DCR_SYNC_BASE_URL: "https://loket.lblod.info" # or another endpoint
DCR_SYNC_LOGIN_ENDPOINT: "https://loket.lblod.info/sync/worship-services-sensitive/login" # or another endpoint
DCR_SECRET_KEY: "key-of-the-producer"
DCR_LANDING_ZONE_DATABASE: "triplestore" # for the initial sync, we go directly to virtuoso
DCR_REMAPPING_DATABASE: "triplestore" # for the initial sync, we go directly to virtuoso
DCR_DISABLE_INITIAL_SYNC: "false"
DCR_DISABLE_DELTA_INGEST: "false"
Then:
drc up -d triplestore migrations
drc up -d db mandatarissen-consumer leidinggevenden-consumer worship-services-main-info-consumer worship-services-private-info-consumer
# Wait until success of the previous step
Then, update docker-compose.override.yml to:
mandatarissen-consumer:
environment:
DCR_SYNC_BASE_URL: "https://loket.lblod.info" # or another endpoint
DCR_LANDING_ZONE_DATABASE: "db"
DCR_REMAPPING_DATABASE: "db"
DCR_DISABLE_DELTA_INGEST: "false"
DCR_DISABLE_INITIAL_SYNC: "false"
leidinggevenden-consumer:
environment:
DCR_SYNC_BASE_URL: "https://loket.lblod.info" # choose the correct endpoint
DCR_LANDING_ZONE_DATABASE: "db"
DCR_REMAPPING_DATABASE: "db"
DCR_DISABLE_DELTA_INGEST: "false"
DCR_DISABLE_INITIAL_SYNC: "false"
worship-services-main-info-consumer:
environment:
DCR_SYNC_BASE_URL: "https://loket.lblod.info" # or another endpoint
DCR_SYNC_LOGIN_ENDPOINT: "https://loket.lblod.info/sync/worship-services-sensitive/login" # or another endpoint
DCR_SECRET_KEY: "key-of-the-producer"
DCR_LANDING_ZONE_DATABASE: "db"
DCR_REMAPPING_DATABASE: "db"
DCR_DISABLE_DELTA_INGEST: "false"
DCR_DISABLE_INITIAL_SYNC: "false"
worship-services-private-info-consumer:
environment:
DCR_SYNC_BASE_URL: "https://loket.lblod.info" # or another endpoint
DCR_SYNC_LOGIN_ENDPOINT: "https://loket.lblod.info/sync/worship-services-sensitive/login" # or another endpoint
DCR_SECRET_KEY: "key-of-the-producer"
DCR_LANDING_ZONE_DATABASE: "database"
DCR_REMAPPING_DATABASE: "database"
DCR_DISABLE_DELTA_INGEST: "false"
DCR_DISABLE_INITIAL_SYNC: "false"
drc up -d
sh scripts/reset-elastic.sh
1.28.5 (2025-01-23)
Frontend
- Bump to v1.28.3
Backend
- Datafix: correct merger change events for worship organisations (OP-3534)
- Avoid municipality filter to include partial matches (OP-3509)
Deploy notes
drc restart migrations-triggering-indexing; drc logs -ft --tail=200 migrations-triggering-indexingdrc pull frontend; drc up -d frontend- Perform a full re-index by executing
./scripts/reset-elastic.sh
1.28.4 (2025-01-16)
Backend
Data
- Performance fix on 1.28.3 [DL-6377]
Deploy commands
drc restart migrations
drc exec delta-producer-background-jobs-initiator curl -X POST http://localhost/public/healing-jobs # or wait for the healing to kick in
1.28.3 (2025-01-16)
Backend
Data
- Datafix. Fusiegemeentes had different bestuursfuncties attached to OCMW and Gemeente. [DL-6377] However, business-rule-wise, these bestuursfuncties are shared.
Deploy commands
drc restart migrations
drc exec delta-producer-background-jobs-initiator curl -X POST http://localhost/public/healing-jobs # or wait for the healing to kick in
1.28.2 (2025-01-13)
Backend
- Added "Opdrachthoudende vereniging met private deelname" in delta public (DL-6368)
Deploy commands
drc restart migrations
drc exec delta-producer-background-jobs-initiator curl -X POST http://localhost/public/healing-jobs # or wait for the healing to kick in
1.28.1 (2025-01-11)
Backend
- Import 2025 NIS codes and update werkingsgebieden (OP-3342)
- Add merger change events for merged police zones (OP-3454)
- Delete local involvements for worship services (OP-3501, OP-3512)
- Move link between new municipalities and province to shared graph (OP-3513, OP-3514)
Deploy notes
- Restart both migration services
Docker commands
drc restart migrations; drc logs -ft --tail=200 migrationsdrc restart migrations-triggering-indexing; drc logs -ft --tail=200 migrations-triggering-indexing
1.28.0 (2025-01-02)
Backend
- Bump frontend to
v1.28.0 - Add end date for governing bodies for municipalities and OCMWs and update status (OP-3348)
- Update municipality and province name in organisation's addresses (OP-3410)
- Add merger change events for merged municipalities and OCMWs (OP-3412)
- Updates names for merged municipalities and OCMWs (OP-3456)
Deploy notes
- Restart both migration services
- Bump frontend
Docker commands
drc restart migrations; drc logs -ft --tail=200 migrationsdrc restart migrations-triggering-indexing; drc logs -ft --tail=200 migrations-triggering-indexingdrc pull frontend; drc up -d frontend