list via cli and creation date
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 113
- Forks
- 22
- Avg merge
- 10h 40m
- Merged PRs (30d)
- 13
Description
Is your feature request related to a problem?
would be nice to be able to do unraid-api apikey --list to show list of apikeys for triage purposes...
maybe hidden argument to show system (hidden) ones as well?
additionally add/expose the apikey creation date on the gui/cli as that info is stored just have to jump through hoops to lookup
# cat /boot/config/plugins/dynamix.my.servers/keys/*
{
"createdAt": "2025-09-10T21:22:32.400Z",
"description": "nzb360",
...
Is your feature request related to a problem?
triage purposes when someone notices an apikey is added to their system and trying to figure out why. can help correlate things.
Describe the solution you'd like
expose info easier
Describe alternatives you've considered
none
Additional context
recent talk in unraid api discord channel
Environment (if relevant)
Unraid OS Version:
any
Pre-submission Checklist
- I have searched existing issues to ensure this feature hasn't already been requested
- This is not an Unraid Connect related feature (if it is, please submit via the support form instead)
- I have provided clear examples or use cases for the feature
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing apikey CLI and GUI entry points, then inspect the stored records under /boot/config/plugins/dynamix.my.servers/keys/*. Confirm how current API keys are discovered and represented. Done means users can list keys for triage, optionally account for hidden system keys, and see each key's creation date through the requested interfaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, cli, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100