alex
8b4784f5ed
- Archive config-secrets (FN-009) - 31 tasks complete - Archive runfusion-poc (FN-008) - 25 tasks complete - Archive deployment-config (FN-006) - 27 tasks complete - All changes moved to openspec/changes/archive/
1.6 KiB
1.6 KiB
ADDED Requirements
Requirement: Configs are mounted into tool containers
The system SHALL mount configuration values as files into spawned tool containers.
Scenario: Config file mount
- WHEN a tool instance is spawned
- THEN all applicable configs are written to /app/config/
- AND each config is a separate JSON file named by key
- AND files have restrictive permissions (0400)
Scenario: Config scope resolution
- WHEN configs are resolved for a tool instance
- THEN the system collects configs from all applicable scopes
- AND instance scope overrides project scope
- AND project scope overrides user scope
- AND user scope overrides global scope
Requirement: Secrets are injected as environment variables
The system SHALL inject secret values as environment variables into tool containers.
Scenario: Secret env var injection
- WHEN a tool instance is spawned
- THEN all applicable secrets are decrypted
- AND injected as environment variables with uppercase keys
- AND the container process can access them
Scenario: Secret scope resolution
- WHEN secrets are resolved for a tool instance
- THEN the same scope hierarchy applies as configs
- AND closest scope wins on key collision
Requirement: Missing secrets fail spawn
The system SHALL prevent spawning if referenced secrets are missing.
Scenario: Validate secrets before spawn
- WHEN a spawn request references a secret by key
- AND the secret does not exist in any applicable scope
- THEN the spawn fails with a clear error message
- AND no container is created