fix(cli): add --header flag to all CLI subcommands that make RPC calls
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 344
- Forks
- 47
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 26
Description
Summary
Many CLI subcommands that make RPC calls are missing the --header / -H flag, making it impossible to pass authentication headers (e.g., session cookies). Only create subcommands and preferences commands currently support it.
Affected commands
| Command | create |
list |
view |
edit |
|---|---|---|---|---|
organization |
-H | missing | missing | missing |
project |
-H | missing | missing | missing |
group |
-H | missing | missing | missing |
user |
-H | missing | missing | missing |
role |
-H | missing | missing | missing |
permission |
-H | missing | missing | missing |
policy |
-H | missing | - | missing |
namespace |
- | missing | missing | - |
preferences |
- | -H | -H | -H |
Expected behavior
All subcommands that make RPC calls should support --header / -H for passing authentication headers:
./frontier organization list -H "Cookie:sid=<session>"
./frontier user view <id> -H "Cookie:sid=<session>"
./frontier namespace list -H "Cookie:sid=<session>"
🤖 Generated with Claude Code
Contributor guide
No contributing guide indexed for this repository
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 with the existing header handling in the CLI's create subcommands and preferences commands, then inspect the organization, project, group, user, role, permission, policy, and namespace list/view/edit entry points. Confirm that every listed subcommand making an RPC call accepts --header/-H and that the documented authentication-header examples work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100