Partner Credentials
Operations
Deployments, SLOs, and monitoring for Partner Credentials
Deployments
- Build from
services/partnercreds/Dockerfile. - The container runs
granianagainstservices.partnercreds.main:app. - Default listen port is
8080and honors thePORTenvironment variable.
Startup behavior
- Loads
PARTNERCREDS_SENTRY_DSNfrom Secret Manager. - Initializes Spanner client and warms the connection pool.
- Initializes the token cache manager and partner token fetchers.
Monitoring and alerts
- Sentry is required; startup fails if the DSN is missing.
- Logs are emitted in structured JSON format (local dev uses text logs).
SLOs and SLIs
- TBD. Define latency and error targets for token issuance.
Scaling and performance
- Stateless service with in-memory token cache per instance.
- Token refreshes are scheduled before expiry to avoid cold token fetches.
- Partner API timeouts prevent long request stalls.
Last updated on