feat: config sync worker endpoint | LLMO-3918 by calvarezg · Pull Request #2048 · adobe/spacecat-api-service

calvarezg · 2026-03-26T22:22:07Z

Description

Adds SQS-based triggering of the S3-to-Postgres config sync after every config save, plus an on-demand HTTP endpoint to manually trigger it.

SQS trigger on config save

After a successful updateLlmoConfig S3 write, an llmo-config-db-sync SQS message is dispatched to the audit jobs queue — gated by a hardcoded ALLOWED_SITE_IDS constant (placeholder UUIDs — must be replaced before deploy).

On-demand sync endpoint

POST /v2/orgs/:spaceCatId/sync-config?siteId=<uuid> — validates the organization, site ownership, user access, and site gating before enqueuing the same SQS message.

Changes

Modified: src/controllers/llmo/llmo.js — added ALLOWED_SITE_IDS constant, isSyncEnabledForSite helper, and SQS dispatch after S3 write in updateLlmoConfig
Modified: src/controllers/brands.js — added ALLOWED_SITE_IDS constant, isSyncEnabledForSite helper, and triggerConfigSync handler
Modified: src/routes/index.js — registered POST /v2/orgs/:spaceCatId/sync-config
Modified: test/controllers/llmo/llmo.test.js — tests for SQS dispatch gating
Modified: test/controllers/brands.test.js — tests for triggerConfigSync endpoint (13 scenarios)

Related Issues

LLMO-3918

make sure to link the related issues in this description. Or if there's no issue created, make sure you
describe here the problem you're solving.
when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes

If the PR is changing the API specification:

make sure you add a "Not implemented yet" note the endpoint description, if the implementation is not ready
yet. Ideally, return a 501 status code with a message explaining the feature is not implemented yet.
make sure you add at least one example of the request and response.

If the PR is changing the API implementation or an entity exposed through the API:

make sure you update the API specification and the examples to reflect the changes.

If the PR is introducing a new audit type:

make sure you update the API specification with the type, schema of the audit result and an example

github-actions · 2026-03-26T22:38:12Z

This PR will trigger a patch release when merged.

codecov · 2026-03-26T22:41:06Z

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

…DB sync. Added 'dryRun' parameter handling and updated logging to reflect dry run status.

…clude a new site ID for development purposes.

…ogs for both triggering and skipping sync based on site ID allowance.

…-to-DB config sync message.

…g sync, marking it as temporary for future adjustment.

vivesing · 2026-03-31T04:40:34Z


+  // Temporary: hardcoded site IDs for which the S3-to-DB config sync is enabled.
+  // TODO: replace with actual site UUIDs per environment.
+  const ALLOWED_SITE_IDS = [


should we keep both allowed sites at a single place and can be imported here.

vivesing · 2026-03-31T04:42:27Z

+
+      const isDryRun = dryRun === 'true';
+      await context.sqs.sendMessage(context.env.AUDIT_JOBS_QUEUE_URL, {
+        type: 'llmo-config-db-sync',


should we create a const for the topic name to be used everywhere from a single place?

vivesing · 2026-03-31T04:45:30Z

  'PATCH /v2/orgs/:spaceCatId/brands/:brandId/prompts/:promptId': 'organization:write',
  'DELETE /v2/orgs/:spaceCatId/brands/:brandId/prompts/:promptId': 'organization:write',
  'POST /v2/orgs/:spaceCatId/brands/:brandId/prompts/delete': 'organization:write',
+  'POST /v2/orgs/:spaceCatId/sync-config': 'organization:write',


Since these configs are site scoped I think we need to include siteId in the api path something like:
/v2/orgs/:spaceCatId/sites/:siteId/sync-config

- Changed the endpoint for triggering config sync to include siteId in the URL. - Removed hardcoded site IDs and moved the sync check logic to a new constants file. - Updated logging to use a constant for the sync type. - Adjusted tests to reflect the new parameter structure and ensure proper validation for siteId.

…est case

…adjust corresponding test case

# [1.391.0](v1.390.2...v1.391.0) (2026-03-31) ### Features * config sync worker endpoint | LLMO-3918 ([#2048](#2048)) ([32d5a5e](32d5a5e))

solaris007 · 2026-03-31T19:15:03Z

🎉 This PR is included in version 1.391.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

## Description Adds SQS-based triggering of the S3-to-Postgres config sync after every config save, plus an on-demand HTTP endpoint to manually trigger it. ### SQS trigger on config save After a successful `updateLlmoConfig` S3 write, an `llmo-config-db-sync` SQS message is dispatched to the audit jobs queue — gated by a hardcoded `ALLOWED_SITE_IDS` constant (placeholder UUIDs — must be replaced before deploy). ### On-demand sync endpoint `POST /v2/orgs/:spaceCatId/sync-config?siteId=<uuid>` — validates the organization, site ownership, user access, and site gating before enqueuing the same SQS message. ### Changes - **Modified**: `src/controllers/llmo/llmo.js` — added `ALLOWED_SITE_IDS` constant, `isSyncEnabledForSite` helper, and SQS dispatch after S3 write in `updateLlmoConfig` - **Modified**: `src/controllers/brands.js` — added `ALLOWED_SITE_IDS` constant, `isSyncEnabledForSite` helper, and `triggerConfigSync` handler - **Modified**: `src/routes/index.js` — registered `POST /v2/orgs/:spaceCatId/sync-config` - **Modified**: `test/controllers/llmo/llmo.test.js` — tests for SQS dispatch gating - **Modified**: `test/controllers/brands.test.js` — tests for `triggerConfigSync` endpoint (13 scenarios) ## Related Issues [LLMO-3918](https://jira.corp.adobe.com/browse/LLMO-3918) - [ ] make sure to link the related issues in this description. Or if there's no issue created, make sure you describe here the problem you're solving. - [ ] when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes If the PR is changing the API specification: - [ ] make sure you add a "Not implemented yet" note the endpoint description, if the implementation is not ready yet. Ideally, return a 501 status code with a message explaining the feature is not implemented yet. - [ ] make sure you add at least one example of the request and response. If the PR is changing the API implementation or an entity exposed through the API: - [ ] make sure you update the API specification and the examples to reflect the changes. If the PR is introducing a new audit type: - [ ] make sure you update the API specification with the type, schema of the audit result and an example

# [1.391.0](v1.390.2...v1.391.0) (2026-03-31) ### Features * config sync worker endpoint | LLMO-3918 ([#2048](#2048)) ([32d5a5e](32d5a5e))

config sync worker process

793d56c

calvarezg changed the title ~~config sync worker process~~ feat: config sync worker endpoint | LLMO-3918 Mar 26, 2026

test fix

34a7b96

calvarezg marked this pull request as draft March 26, 2026 22:37

calvarezg self-assigned this Mar 26, 2026

calvarezg added the enhancement New feature or request label Mar 26, 2026

calvarezg added 10 commits March 30, 2026 09:20

Merge branch 'main' into feat/LLMO-3918-config-sync

ae94908

Enhance BrandsController to support dry run functionality for config …

32bffc5

…DB sync. Added 'dryRun' parameter handling and updated logging to reflect dry run status.

Update allowed site IDs in BrandsController and LLMO controller to in…

633dea3

…clude a new site ID for development purposes.

Enhance LlmoController logging for S3-to-DB config sync. Added info l…

fcdb78f

…ogs for both triggering and skipping sync based on site ID allowance.

tests

d0486b1

tests

3486aa5

Refactor logging in LlmoController to remove redundant brackets in S3…

a7ad997

…-to-DB config sync message.

Update LlmoController to clarify 'dryRun' parameter in S3-to-DB confi…

53d3b54

…g sync, marking it as temporary for future adjustment.

Merge branch 'main' into feat/LLMO-3918-config-sync

3c8c68a

Merge branch 'main' into feat/LLMO-3918-config-sync

c856edf

calvarezg marked this pull request as ready for review March 30, 2026 18:23

vivesing reviewed Mar 31, 2026

View reviewed changes

vivesing approved these changes Mar 31, 2026

View reviewed changes

calvarezg added 7 commits March 31, 2026 10:35

Merge branch 'main' into feat/LLMO-3918-config-sync

f1b4e5f

add prod site id

87b9601

Merge branch 'main' into feat/LLMO-3918-config-sync

fd40770

fix: set dryRun to false in LlmoController for config sync

03976c3

back to dry run

f415624

fix test to dry run set to true

c949f58

calvarezg added 4 commits March 31, 2026 17:37

fix: set dryRun to false in LlmoController and update corresponding t…

e4ffb33

…est case

Merge branch 'main' into feat/LLMO-3918-config-sync

958ef2e

fix: update LlmoController to set dryRun to true for config sync and …

fb311ef

…adjust corresponding test case

Merge branch 'main' into feat/LLMO-3918-config-sync

a496065

calvarezg merged commit 32d5a5e into main Mar 31, 2026
20 checks passed

calvarezg deleted the feat/LLMO-3918-config-sync branch March 31, 2026 19:08

solaris007 pushed a commit that referenced this pull request Mar 31, 2026

chore(release): 1.391.0 [skip ci]

5ac9a00

# [1.391.0](v1.390.2...v1.391.0) (2026-03-31) ### Features * config sync worker endpoint | LLMO-3918 ([#2048](#2048)) ([32d5a5e](32d5a5e))

solaris007 added the released label Mar 31, 2026

ravverma pushed a commit that referenced this pull request Apr 6, 2026

chore(release): 1.391.0 [skip ci]

778804a

# [1.391.0](v1.390.2...v1.391.0) (2026-03-31) ### Features * config sync worker endpoint | LLMO-3918 ([#2048](#2048)) ([32d5a5e](32d5a5e))

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: config sync worker endpoint | LLMO-3918#2048

feat: config sync worker endpoint | LLMO-3918#2048
calvarezg merged 23 commits intomainfrom
feat/LLMO-3918-config-sync

calvarezg commented Mar 26, 2026

Uh oh!

github-actions Bot commented Mar 26, 2026 •

edited

Loading

Uh oh!

codecov Bot commented Mar 26, 2026

Uh oh!

vivesing Mar 31, 2026

Uh oh!

vivesing Mar 31, 2026

Uh oh!

vivesing Mar 31, 2026

Uh oh!

Uh oh!

solaris007 commented Mar 31, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

calvarezg commented Mar 26, 2026

Description

SQS trigger on config save

On-demand sync endpoint

Changes

Related Issues

Uh oh!

github-actions Bot commented Mar 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

codecov Bot commented Mar 26, 2026

Codecov Report

Uh oh!

vivesing Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

vivesing Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

vivesing Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

solaris007 commented Mar 31, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

github-actions Bot commented Mar 26, 2026 •

edited

Loading