Missing --unencrypted-regex option
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
The --encrypted-regex option already exists. Why does the equivalent exist for unencrypted keys ?
It would be more flexible than using the --unencrypted-suffix option that forces to have only one suffix value
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 locating the existing --encrypted-regex option and the handling for --unencrypted-suffix in the command-line interface. Compare their behavior and determine the expected equivalent for unencrypted keys; done means the new option is accepted and provides regex-based selection without the suffix limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100