Add unit tests for Router configuration and transport layers
- Implemented tests for RouterConfig, RoutingOptions, StaticInstanceConfig, and RouterConfigOptions to ensure default values are set correctly. - Added tests for RouterConfigProvider to validate configurations and ensure defaults are returned when no file is specified. - Created tests for ConfigValidationResult to check success and error scenarios. - Developed tests for ServiceCollectionExtensions to verify service registration for RouterConfig. - Introduced UdpTransportTests to validate serialization, connection, request-response, and error handling in UDP transport. - Added scripts for signing authority gaps and hashing DevPortal SDK snippets.
This commit is contained in:
9
docs/governance/SHA256SUMS
Normal file
9
docs/governance/SHA256SUMS
Normal file
@@ -0,0 +1,9 @@
|
||||
# Hash index for governance/exception docs
|
||||
# <sha256> <relative-path>
|
||||
8a5d1429a307eff95d86476e330defb381bc447239e569bea8c2b641db72ff98 docs/governance/exceptions.md
|
||||
bc91b827793ea36a079b0f68de102424034f539d497f50fa90cb8a6c4da4dec4 docs/governance/approvals-and-routing.md
|
||||
ec33d6612473d997196ec463042cc5cff21e107ab9d267fd2fa4ffd166e6f25c docs/api/exceptions.md
|
||||
147b79a89bc3c0561f070e843bc9aeb693f12bea287c002073b5f94fc7389c5f docs/ui/exception-center.md
|
||||
9967d66765f90a31e16d354e43dd6952566d3a359e3250f4f5f9d4b206ba1686 docs/modules/cli/guides/exceptions.md
|
||||
8a5d1429a307eff95d86476e330defb381bc447239e569bea8c2b641db72ff98 docs/governance/exceptions.md
|
||||
bc91b827793ea36a079b0f68de102424034f539d497f50fa90cb8a6c4da4dec4 docs/governance/approvals-and-routing.md
|
||||
15
docs/governance/approvals-and-routing.md
Normal file
15
docs/governance/approvals-and-routing.md
Normal file
@@ -0,0 +1,15 @@
|
||||
# Approvals & Routing (stub)
|
||||
|
||||
> Status: BLOCKED — awaiting routing matrix, MFA rules, audit trail requirements (DOCS-EXC-25-002).
|
||||
|
||||
## Outline
|
||||
1. Roles and approvers (matrix TBD)
|
||||
2. Routing rules per tenant/environment/resource
|
||||
3. MFA requirements and enforcement points
|
||||
4. Audit trail fields and retention
|
||||
5. Offline readiness (export/import of approvals)
|
||||
6. Verification steps (hash list + sample events)
|
||||
|
||||
## Determinism
|
||||
- Add hashes to `docs/governance/SHA256SUMS` when populated.
|
||||
- Keep tables sorted by role/tenant/environment to minimize churn.
|
||||
24
docs/governance/exceptions.md
Normal file
24
docs/governance/exceptions.md
Normal file
@@ -0,0 +1,24 @@
|
||||
# Exception Governance (stub)
|
||||
|
||||
> Status: BLOCKED — awaiting lifecycle/routing matrix and API contract from Governance/Authority/Platform guilds. This stub sets structure and determinism requirements for DOCS-EXC-25-001.
|
||||
|
||||
## Scope
|
||||
- Exception lifecycle, scope patterns, compliance checklist.
|
||||
- Deterministic artifacts for offline/air-gap use.
|
||||
|
||||
## Pending inputs
|
||||
- Final lifecycle states and transitions.
|
||||
- Scope pattern examples (tenant/env/service/resource).
|
||||
- Compliance checklist from Governance Guild.
|
||||
|
||||
## Outline
|
||||
1. Imposed rule banner (to be filled)
|
||||
2. Exception lifecycle (states, transitions, allowed actors)
|
||||
3. Scope patterns and examples
|
||||
4. Compliance checklist
|
||||
5. Offline/air-gap packaging notes
|
||||
6. Verification (hash + replay of fixtures)
|
||||
|
||||
## Determinism
|
||||
- When content is added, record hashes in `docs/governance/SHA256SUMS`.
|
||||
- Use UTC timestamps and stable ordering of tables.
|
||||
Reference in New Issue
Block a user