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
feat: add RegradeResource RPC — re-apply tier connection caps to live Postgres roles (#8)
A plan upgrade flips resources.tier but never re-applies the HARD
infrastructure limits baked at provision time — the Postgres role
CONNECTION LIMIT in particular. RegradeResource closes that gap:
* server.go — RegradeResource handler dispatches to the postgres
backend; non-postgres types return applied=false + skip_reason.
* backend/postgres — Regrade() ALTERs the role CONNECTION LIMIT to
the tier-entitled cap from instant.dev/common/plans. K8sBackend
is fail-soft when the customer pod is unreachable (returns
applied=false so the caller retries on the next sweep).
Idempotent: re-applying the same limit is a no-op. 3 new server tests.
Phase 1 of the entitlement re-grade work. Requires the matching proto
change (RegradeResource RPC) — CI builds check out proto@master, so
the proto PR must merge before this one's CI goes green.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments