chore: archive project-management and scaffold user-profile change
This commit is contained in:
@@ -3,9 +3,7 @@
|
||||
## Purpose
|
||||
|
||||
Generate and manage SSH keys for git operations with external providers.
|
||||
|
||||
## Requirements
|
||||
|
||||
### Requirement: Key Generation
|
||||
|
||||
The system SHALL generate Ed25519 SSH key pairs.
|
||||
@@ -18,18 +16,17 @@ The system SHALL generate Ed25519 SSH key pairs.
|
||||
- AND the public key is stored in OpenSSH format
|
||||
|
||||
### Requirement: Key Association
|
||||
The system SHALL only allow project default-key assignment using keys valid for the authenticated owner's project scope.
|
||||
|
||||
The system SHALL support user-level and project-level keys.
|
||||
#### Scenario: Valid default key assignment
|
||||
- GIVEN a project owner and an eligible SSH key
|
||||
- WHEN the owner sets the key as default for the project
|
||||
- THEN the project stores that key reference
|
||||
|
||||
#### Scenario: User-level key
|
||||
- GIVEN an authenticated user
|
||||
- WHEN they generate a key without specifying a project
|
||||
- THEN it's associated with their user account
|
||||
|
||||
#### Scenario: Project-level key
|
||||
- GIVEN an authenticated user with a project
|
||||
- WHEN they generate a key for that project
|
||||
- THEN it's associated with the project
|
||||
#### Scenario: Invalid default key assignment
|
||||
- GIVEN a project owner
|
||||
- WHEN the owner attempts to set an ineligible SSH key as project default
|
||||
- THEN the system responds with validation failure
|
||||
|
||||
### Requirement: Key Display
|
||||
|
||||
|
||||
Reference in New Issue
Block a user