70febffe1a
The seam keeps the telemetry/redact scrubbing interface but ships no rules of its own: the innermost next() passes records through unchanged, and deployments mount their rules as waterfall listeners. As an SDK we cannot know which patterns are secrets in a given deployment; a shipped list invites false confidence while catching only known shapes, and false positives would corrupt exported bodies. Mechanism stays with the seam, policy moves to the deployment; both READMEs and the Agent Note state the raw-export default plainly. The loader-composition e2e now mounts a deployment-style rule fixture and pins the same wire behavior: secret absent, placeholder present, canonical log untouched.
29 lines
866 B
YAML
29 lines
866 B
YAML
# Test-only composition: session-telemetry-otel through the real Loader/app
|
|
# path, exporting to the mock OTLP collector the driver starts (url via env).
|
|
# The redact-rule entry models a deployment mounting its own scrub rule on the
|
|
# telemetry/redact waterfall — the seam itself ships no rules.
|
|
- id: cli-mock-llm
|
|
name: './cli-mock-llm.ts'
|
|
|
|
- id: telemetry-redact-rule
|
|
name: './telemetry-redact-rule.ts'
|
|
|
|
- id: bash
|
|
name: '@deepseek-ai/dsh-bash-local'
|
|
|
|
- id: telemetry-otel
|
|
name: '@deepseek-ai/dsh-session-telemetry-otel'
|
|
config:
|
|
exporter:
|
|
url: !!js process.env.DSH_TELEMETRY_E2E_URL
|
|
|
|
- id: cli-agent
|
|
name: '@deepseek-ai/dsh-cli-demo'
|
|
config:
|
|
provider: cli-mock
|
|
model: cli-mock
|
|
persona: 'Test the session-telemetry-otel plugin.'
|
|
persistenceRoot: './.sessions'
|
|
persistenceCompression: 'none'
|
|
workspaceContext: false
|