Repository navigation
feat(business-site): move the tenant to the signed v3.4.0 release - #6349
Conversation
v3.4.0 carries business-site#598: the ExternalSecrets that project the Numina and Stripe credentials from OpenBao into the business-site namespace, and egress to api.numina.app and api.stripe.com. It also carries the portal billing work (#599, #600). Every payment and portal gate stays off by default, and nothing mounts the projected secrets yet. Prepared with scripts/bootstrap-tenant-source.sh --prepare-canonical-upgrade against the read-only production context. Same approved publisher revision; no new approval. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ledger The pinned kubectl / Kustomize render in CI changes exactly one ledger entry: Tenant flux-system/business-site, whose source digest moves to the v3.4.0 manifests. No authorization resource is added or removed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@codex review for Tenant source digest bump to business-site v3.4.0: check the canonical binding (published-upgrade with previousBinding/previousObservation), the scan-baseline INSTANCE-CONTENT hash and the single authorization-ledger entry all match the new digest, and that nothing widens authorization |
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Nice work! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
✅
|
✅
|

What
Moves the business-site Tenant to the signed v3.4.0 release (source
4f0d66f). The publisher revisiona76d5dfis unchanged, so no new approval is needed.v3.4.0 carries devantler-tech/business-site#598:
business-site-numinaandbusiness-site-stripe, which project the Numina and Stripe credentials from OpenBao (apps/business-site/numina,apps/business-site/stripe) into thebusiness-sitenamespace. feat(business-site): let the tenant read its billing keys and resolve their APIs #6339 granted the platform role read access to them.api.numina.appandapi.stripe.com.It also carries the portal billing work (devantler-tech/business-site#599, devantler-tech/business-site#600).
Every payment and portal gate stays off by default, and nothing mounts the projected secrets yet.
How it was prepared
scripts/bootstrap-tenant-source.sh --prepare-canonical-upgrade --tag v3.4.0ran against the read-only production context. It verified the signed manifestssha256:9d444d10…0516, which were published by run 43728348739, attempt 2, of the release-triggeredpublish-runtime.yaml, and it wrotetenant.yamlandcanonical-tenant-source-bindings.json.INSTANCE-CONTENThash is recomputed the same wayscan-rgd-templates.shcomputes it.flux-system/business-site, to the hash from CI's pinned render, as in feat(business-site): move the tenant to the signed v3.3.0 release #6315. No authorization resource is added or removed.After merge
Once Flux reconciles, I'll check that both ExternalSecrets report
Ready/SecretSynced, using status conditions and key names only. I'll also re-check www, trailing-slash and 404 parity, and that the portal still answers 404.🤖 Generated with Claude Code