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/
38 lines
1.3 KiB
Markdown
38 lines
1.3 KiB
Markdown
## 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
|