Governance Service Configuration
Governance Service configuration is managed through the deployment chart and customer environment values. This page describes the configuration areas operators should understand before release.
Required Configuration Areas
Section titled “Required Configuration Areas”- Auth Service connection for identity and authorization checks.
- Platform database connection for durable governance records.
- Object storage provider for attachments.
- Integrity Service connection for credential and lineage workflows.
- PDF generation service connection for downloadable reports.
Object Storage
Section titled “Object Storage”Supported attachment storage providers are Azure Blob Storage, Google Cloud Storage, AWS S3, and a mock provider for local or non-production use.
Use production-grade object storage for customer environments. Confirm bucket or container access before enabling attachment-heavy workflows.
Identity Provider Alignment
Section titled “Identity Provider Alignment”Governance Service does not replace Auth Service. It must be configured to trust the Auth Service deployment that owns users, roles, API keys, and service accounts.
Operational Settings
Section titled “Operational Settings”Operators should confirm health checks, readiness behavior, idempotency settings, database migration behavior, and upgrade notes before release. Keep customer-specific secrets out of product documentation and store them in the deployment’s secret management system.