Skip to content

Draft: POC - Synchronizing catalog_resources with projects

Leaminn Ma requested to merge poc-sync-catalog-resources-projects into master

What does this MR do and why?

This is the first iteration POC for the background syncing process proposed in #429376 (closed).

Objectives:

  • It ensures the denormalized columns of catalog_resources (name, description, and visibility level) are in sync with projects when:
    • A new catalog resource is created.
    • There are updates to those columns in projects.
    • It updates catalog_resources.latest_released_at when a catalog resource version is deleted.

UPDATE [2023-11-21]:

This implementation will be adjusted so that catalog_resources.latest_released_at is updated directly via DB triggers rather than utilizing the SyncEvent process. Details in !137238 (comment 1661575852).

How to set up and validate locally

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #429376 (closed)

Edited by Leaminn Ma

Merge request reports