-
Notifications
You must be signed in to change notification settings - Fork 25
Labels
enhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomersuser experience
Description
spike secret list and spike policy list have inconsistent output behavior. The secret list command shows only paths (concise), while the policy list command dumps entire policy objects (verbose).
For consistency and usability, spike policy list should show only policy names and IDs.
Current Behavior:
spike secret list - Concise output:
secrets/db/creds
secrets/app/config
secrets/cache/redis
spike policy list - Verbose output (dumps entire policy objects):
- name: "database-policy"
spiffeidPattern: "^spiffe://example\\.org/database$"
pathPattern: "^secrets/database/production$"
permissions: [read]
- name: "web-service-policy"
spiffeidPattern: "^spiffe://example\\.org/web-service$"
pathPattern: "^secrets/web-service/config$"
permissions: [read, write]
...
Expected Behavior
spike policy list should show only names and IDs:
ID NAME
550e8400-e29b-41d4-a716-446655440000 database-policy
6ba7b810-9dad-11d1-80b4-00c04fd430c8 web-service-policy
Users can then use spike policy get to retrieve full policy details when needed.
Rationale
- Consistency: Both list commands should follow the same pattern (concise summary)
- Usability: Policy lists can grow large; dumping full objects makes output hard to scan
- Separation of concerns: List operations should enumerate resources; get operations should show details
- CLI conventions: Standard practice is for list to show identifiers and get/describe to show details
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomersuser experience