Files
headquarter/openspec/changes/config-secrets/specs/config-management/spec.md
T
alex 78aaddb2b5
CI / Web CI (push) Failing after 12s
CI / API CI (push) Failing after 1m1s
docs(openspec): add OpenSpec changes for FN-005, FN-006, FN-008, FN-009, FN-010
- Add frontend-foundation change (FN-005) with 46 tasks
- Add deployment-config change (FN-006) with 27 tasks
- Add runfusion-poc/opencode-poc change (FN-008) with 25 tasks
- Add config-secrets change (FN-009) with 31 tasks
- Add codeserver-spawn change (FN-010) with 38 tasks
- Include project specsheet and configuration
- Archive completed deployment-config change
2026-05-14 17:35:20 +02:00

1.3 KiB

ADDED Requirements

Requirement: User can create config values

The system SHALL allow users to create configuration values at various scopes.

Scenario: Create project config

  • WHEN the user navigates to project settings
  • AND clicks "Add Config"
  • THEN a form appears with key, value, and scope fields
  • AND submitting creates a config at the selected scope

Scenario: Config scope validation

  • WHEN the user creates a config
  • THEN the scope must be one of: global, user, project, instance
  • AND the scope_id must match the selected scope type

Requirement: User can view and update configs

The system SHALL display configs with scope-based filtering.

Scenario: List configs

  • WHEN the user views configs for a project
  • THEN all configs visible at project scope or above are displayed
  • AND values are shown as formatted JSON

Scenario: Update config

  • WHEN the user edits a config value
  • THEN the updated value is saved
  • AND the change takes effect on next tool spawn

Requirement: User can delete configs

The system SHALL allow deletion of config values.

Scenario: Delete config

  • WHEN the user clicks delete on a config
  • THEN a confirmation dialog appears
  • AND confirming removes the config
  • AND the config is no longer injected into containers