manifoldco / manifoldco/torus-cli
ACL - Validate ACL Path on allow/deny
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 603
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Unlike `torus set`, `unset`, `view`, and `ls` we *do not* validate that the path used in an ACL through `allow` or `deny` exists -- making it very easy for a user to set a rule against an unknown project, environment, or service.
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 CLI paths for allow and deny, then compare their path handling with set, unset, view, and ls. Done means allow and deny reject unknown project, environment, or service paths consistently instead of creating rules for them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100