alex
78aaddb2b5
- 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
1.3 KiB
1.3 KiB
ADDED Requirements
Requirement: User can create secrets
The system SHALL allow users to store encrypted secret values.
Scenario: Create secret
- WHEN the user navigates to project secrets
- AND clicks "Add Secret"
- THEN a form appears with key and value fields
- AND the value is encrypted with Fernet before storage
- AND the user sees a masked value (e.g., ••••••) after creation
Scenario: Secret scope
- WHEN the user creates a secret
- THEN the scope can be user, project, or instance
- AND the secret is only visible within that scope hierarchy
Requirement: Secrets are never exposed decrypted
The system SHALL prevent decrypted secret values from being sent to the frontend.
Scenario: Secret list display
- WHEN the user views the secrets list
- THEN only secret keys and scopes are visible
- AND values are always masked
Scenario: Secret update
- WHEN the user updates a secret
- THEN only the new value is sent to the backend
- AND the old value is replaced (not displayed)
Requirement: User can delete secrets
The system SHALL allow deletion of secret values.
Scenario: Delete secret
- WHEN the user deletes a secret
- THEN the encrypted value is permanently removed
- AND the secret is no longer injected into containers