Asset Configuration Boundaries
Summary
This page catalogs the configuration categories that influence asset-service behavior and classifies each by how it is governed. It does not list any keys, values, ports, hosts, or secrets. Its purpose is to make explicit which behaviors are required for the service to run, which are optional or defaulted, which are controlled by feature flags, and which apply only in Development. Categories without confirmed production governance are marked Requires confirmation.
Audience
- DevOps engineers preparing environment configuration.
- Solution and security architects reviewing configuration surface.
- Support engineers reasoning about environment-dependent behavior.
Reference Content
Classification legend
- Required — the service cannot operate correctly without it.
- Optional — enhances behavior but not required to start.
- Defaulted — has a built-in default when unset.
- Feature-controlled — governed by a feature flag.
- Development-only — active only in the Development environment.
- Requires confirmation — production governance not established in source.
Configuration categories
| Category | Classification | Notes |
|---|---|---|
| Database provider (asset schema) | Required | Npgsql connection consumed by AssetDbContext. |
| JWT authentication | Required (as configured) | Multi-key monolith + Identity signing; issuers/audiences from config; endpoints not role-authorized. |
| Tenant context forwarding | Required | Tenant resolved per request; missing tenant maps to HTTP 400. |
| Workflow integration flag | Feature-controlled | Asset-approval workflow flag, default OFF; ON registers typed workflow client. |
| Document integration | Optional | Typed document client registered; used when documents are exercised. |
| Messaging (event bus / outbox) | Required | Registered by shared messaging extension; relay runs as hosted service. |
| Gateway asset-routing flag | Feature-controlled | AssetRouting:UseAssetService governs whether the asset slice routes to asset-service. |
| Feature flags (general) | Feature-controlled | Workflow and gateway flags gate optional integrations. |
| Logging | Defaulted | Structured JSON console logging. |
| Tracing exporters | Optional | Console exporter and OTLP exporter are config-gated. |
| Development seeding | Development-only | Seeder runs only in Development. |
| Backfill (console mode) | Optional | CLI ETL mode; production ownership Requires confirmation. |
Governance gaps
Production ownership for migration application, backfill execution, and exporter targets is not established in source and is classified Requires confirmation. Do not assume defaults are production-appropriate.
Source References
microservices/src/asset-service/Program.csmicroservices/src/shared-kernel/Extensions/MessagingExtensions.csmicroservices/src/gateway-api/Program.cs
Related Articles
See Also
Keywords
asset configuration, feature flags, configuration boundaries, environment governance, requires confirmation
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly