Files
Jonathan Boniface 66c32745aa
Some checks failed
check agents / check (push) Failing after 14s
F02: Assessment report and package (ADR 0014, 0015); register agents in KAB
- Report (cp1-assessment-report-agent 0.2.0, step s7): a model writes the
  Assessment report from facts worked out in code (register, gaps, scorecard,
  rule traces, checks, and what each application is from the Discovery
  package); code sets the verdict and renders the pages. The
  disposition_signoff review point moves from the critic to the report.
- Package (cp1-assessment-package-agent 0.1.1, step s8): after sign-off, every
  step's output in one package, with a register, a gaps register, the
  sign-off record, lineage and a sha256 per part, in code. Page step s9.
- scripts/kab_register_agents.py: registers deployed agents in KAB's agent
  catalog (an in-place workflow update doesn't).
- Runs exec_1b1257380df7 (014) and exec_374d5d577077 (015) completed on
  crucible-kab-dev: critic pass, report figures all in its facts, package
  complete with every digest recomputing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-08 20:19:10 +00:00

34 lines
1.4 KiB
YAML

apiVersion: v1
kind: Secret
metadata:
name: <placeholder_for_agent_name>-secrets
type: Opaque
data:
# Base64 encoded values (NOT RECOMMENDED for sensitive data)
# To encode: echo -n 'your-secret-value' | base64
# Example: api-key: eW91ci1hcGkta2V5LXZhbHVl
stringData:
# Plain text values saved on GitHub Secrets (RECOMMENDED)
# Example:
#
# DB_PASSWORD: ${DB_PASSWORD_GITHUB_SECRET}
# ANOTHER_SECRET: ${ANOTHER_GITHUB_SECRET}
#
# ${DB_PASSWORD_GITHUB_SECRET} and ${ANOTHER_GITHUB_SECRET} must exist as GitHub Secrets
#
# AGENT_INBOUND_TOKEN (runtime 0.25.0 or later): when set, every call to the
# agent must carry it as a bearer token, and other calls get HTTP 401. It is
# a secret, so it goes here, never in the ConfigMap. The platform does not
# send this token to agents yet, so leave it unset for now.
# AGENT_INBOUND_TOKEN: ${AGENT_INBOUND_TOKEN_GITHUB_SECRET}
#
# Telemetry keys are not here: agents send to the platform's OpenTelemetry
# Collector, which holds them.
#
# AGENT_CONTINUATION_KEY (runtime 0.28.0 or later): signs the conversation the
# agent hands the platform when it pauses for a person's approval, so it can
# carry on from there. A long random string, different for each agent. Unset,
# each process makes its own at start-up: an answer that reaches another
# replica, or comes after a restart, runs the step again from the start.
# AGENT_CONTINUATION_KEY: ${AGENT_CONTINUATION_KEY_GITHUB_SECRET}