felix.ruizdearcaute/app-organization-portal
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
3ab27e5d36d7acb13702dfc7cf441fd39a21ca06
app-organization-portal/CHANGELOG.md
mirdono 1d2d69594b Merge branch 'master' into development
2025-03-04 10:43:08 +01:00

12 KiB
Raw Blame History

Changelog

Unreleased

Frontend

  • Bump to version [TODO](Link to frontend release)

Backend

  • Datafix: move status for municipalities and provinces to the shared graph such that it can be read by worship users [OP-3469]

Deploy notes

drc restart migrations; drc logs -ft --tail=200 migrations
drc pull frontend; drc up -d frontend

v1.30.3 (2025-03-04)

Frontend

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

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-service to 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
  • Re-enable contact date editing:
    • remove EMBER_ENABLE_EDIT_CONTACT_DATA_FEATURE flag in docker-compose.override.yml
    • Stop and remove the clb-contact-data-consumer service
    • Remove the clb-contact-data-consumer configuration in docker-compose.override.yml
  • Rebuild the search service before starting the re-indexing
  • To enable the membership functionality:
    • Restart migration service
    • Restart services for which the configuration was changed: resource, dispatcher and db
    • Start the db-cleanup service
    • Pull and restart the frontend
    • Perform a re-index using reset-elastic.sh script

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

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-indexing
  • drc 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 migrations
  • drc 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 migrations
  • drc restart migrations-triggering-indexing; drc logs -ft --tail=200 migrations-triggering-indexing
  • drc pull frontend; drc up -d frontend