You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
🙋 Ask: add the business site's Stripe entry to the secrets store #5080
The business site's Stripe entry is not in the secrets store yet. devantler-tech/business-site#598 (merged today) syncs it, and its merge precondition was that you add it. The Numina entry syncs fine, and the access policy covers both (devantler-tech/platform#6339), so only the Stripe entry is missing. Until it exists, the site's deployment never reports healthy. The public site still serves normally, and card payments stay off. Can you add it, or should I take the Stripe sync out until card payments launch?
Options
A. Add the entry. Create the business site's Stripe entry in the secrets store, with the two values chore(deps): Bump libraries/dotnet-flux-cli from 7055c7e to c0b238a #598 names (the API key and the webhook signing secret). Test-mode values are fine while card payments are off. Nothing else is needed: the sync retries every hour.
B. Remove the Stripe sync for now. I open a pull request in business-site that removes only the Stripe sync from the deployment package. It goes back when card payments are ready. The Numina sync stays.
Recommendation
A, because #598 already planned for it and it needs no code change. Only you hold the Stripe keys.
If unanswered
I change nothing. The site keeps serving, but each run sees the deployment as unhealthy until the entry exists.
The live Stripe sync now reports Ready with a successful refresh, as does the Numina sync. The Stripe specification requests both required properties, and the tenant reconciliation reports Ready and Healthy. This clears the missing-entry blocker. No credential values were read or changed.
Activity
chore: agent-claim #5080 nonce=8ebc43781b75befc8791bbfc05da4703
chore: agent-claim #5080 nonce=827112f8b0cfeb844145f7527fa98db7
devantler commentedon Nov 16, 2026
Your digest reply choosing A means retain the Stripe sync and supply its entry.
The live Stripe sync now reports Ready with a successful refresh, as does the Numina sync. The Stripe specification requests both required properties, and the tenant reconciliation reports Ready and Healthy. This clears the missing-entry blocker. No credential values were read or changed.
chore: agent-claim #5080 nonce=03fd32a1be62481edab2fc5b3b4de586
docs(digests): add the 2026-11-17 changelog (#5090)