Record stable workflow channel and PostgreSQL provisioning foundation #42
No reviewers
Labels
No labels
app-migration
bug
ci-cd
cluster
Documentation
duplicate
enhancement
gpu
invalid
networking
question
security
Storage
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Homelab/Documentation!42
Loading…
Reference in a new issue
No description provided.
Delete branch "kiyi/workflow-channel-postgresql"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Records the owner’s 2026-10-13 decisions and prepared source: the highest-priority shared stable-v1 channel, protected manual published-version promotion/rollback, and reusable PostgreSQL provisioning with one private first-time provisioner bootstrap.
Links workflows#93, implementation PR workflows#94, and its verified commit procedure. Names the private terraform-modules#8 tracker without public links to private content; its foundation is prepared in terraform-modules#9. Describes exact pins before adoption, frozen adapter provenance, unchanged required check names, single runtime-record ownership and the remaining storage-engine/caller/backend/hosted acceptance boundaries.
Adds a dated priority update without pretending to recount the older Roadmap snapshot. No live stable promotion, database/secret provisioning, application deployment or public documentation deployment is claimed.
Validation: npm run check and npm run build passed; public Markdown diff reviewed for secrets/private links; native staged Gitleaks 8.30.1 passed. Changes are confined to docs/*.md.
Reviewed the three changed documentation files at
958ce09713and cross-checked the stable-channel and PostgreSQL foundation claims against the live implementation PRs (workflows#94 and terraform-modules#9). The text distinguishes prepared source from hosted acceptance and live promotion/provisioning, preserves the older dated roadmap tally, and does not expose credentials or private bootstrap details. No documentation-level blocker found. This is COMMENT, not approval: Documentation site checks / validate passed, but Source security / security and Source security / pipeline remain pending at this head. Please re-evaluate all exact-head checks before approval/merge; this review does not establish live channel promotion, database provisioning, or authorize deployment.Updated at
d826153cb0. Merged current main and resolved the decisions-table conflict while preserving the already merged Harbor inventory and workflow v1.34.0 status. The application inventory exactly matches main; the new PR diff remains limited to the workflow-channel/PostgreSQL documentation.Recorded run 624 attempt 2's confirmed protected-tag rejection and linked the prepared native OIDC setup in workflows PR #96. The text separates merged/published channel implementation from pending integration authorization, hosted acceptance and consumer adoption. PostgreSQL bootstrap status is preserved.
Validation at this head: npm run check, npm run build, public diff review and native staged Gitleaks 8.30.1 passed. Hosted checks are pending for the new head; the earlier approval does not establish acceptance of this update. No account configuration, tag move, service provisioning or deployment occurred.
Reviewed the complete exact-head contents of docs/decisions-and-open-work.md, docs/delivery-and-operations.md and docs/roadmap.md at
d826153cb0, and cross-checked implementation PR state for workflows#94 and terraform-modules#9. No documentation-level source blocker identified: the text separates source preparation from live channel promotion and database provisioning, records the protected-tag authorization blocker, and keeps the historical roadmap snapshot dated. terraform-modules#9 still has my blocking non-superuser PostgreSQL membership finding; this documentation review does not clear it or validate provisioning. Exact-head Documentation site validate and both Source security contexts are pending; do not treat this comment as CI/security acceptance, approval, or permission to merge. I attempted a source-only APPROVED review on this SHA, but the guarded review tool rejected it with 'GitcheGumi already reviewed this PR' (his approval is recorded at the earlier958ce09713).Updated in
eca06a8to record the verified 2026-10-13 integration setup. The owner selected shared Bots Code/Releases/Actions Write permissions and explicitly approved creation of both restricted native grants under kiyi. Their saved configuration and generated public audiences are recorded in the workflows setup receipt.The documentation now distinguishes configured grants from the remaining owner-only repository variable entries, source review/merge and hosted protected-write/channel acceptance. No tag or service deployment is claimed. npm run check, npm run build, public diff review and native staged Gitleaks 8.30.1 passed for this documentation update.
Reviewed all three changed Markdown files at
eca06a8079and checked the live workflows #94/#96 and terraform-modules #9 PRs. The new paragraph accurately distinguishes saved restricted integration grants from owner-pending audience variables, source merge and untested protected writes/channel acceptance. The dated roadmap tally remains explicitly historical; no live promotion or provisioning is claimed. No documentation-level source blocker found. My blocking PostgreSQL non-superuser membership finding remains open on terraform-modules #9; this documentation review does not validate that provider apply. I attempted a source-only APPROVED review for this exact head, but the guarded submitter refused it: 'GitcheGumi already reviewed this PR' (his approval is on the older958ce09713). This COMMENT is not approval or merge authorization. Documentation validation and both source-security checks remain pending; exact-head acceptance must be verified separately.