feat(saga-mesh): add sis_db + role to the empty seed profile#112
Merged
Conversation
sis-api (rostering, on main as of 2026-06) owns a dedicated sis_db that the synthetic-dev stack provisions with a local idempotent guard today. Add the canonical role + database here so every mesh consumer gets it without the guard. Mirrors the existing per-app role/db/grant pattern. Tracking: saga-ed/student-data-system sds_92 decision d1.7. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Add the
sisrole +sis_dbdatabase (with grant) to the saga-meshprofile-empty.sqlseed, mirroring the existing per-app role/db/grantpattern for iam/programs/scheduling/ads_adm/ledger.
Why
Adam's sis-api landed in
rosteringonmain(2026-06). It owns adedicated
sis_dband needs the role/database to exist before its prismamigrations deploy. The sds_92 synthetic-dev stack currently provisions
this with a local idempotent guard (
up.sh'sensure_sis_db); thisPR adds it to the canonical seed so every mesh consumer gets it without
the guard. Once this is on main, the local guard can be dropped.
Verification
Applied the equivalent role+db SQL against a live
soa-postgres-1mesh,deployed the sis-db init migration into
sis_db, and booted sis-api:/health/ready→ 200{"status":"ready","sisDb":"connected"}.Tracking: saga-ed/student-data-system sds_92 decision
d1.7.