letsencrypt / letsencrypt/boulder
consider using a command line parsing library
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
Right now we depend solely on Go's built-in flag package. That's because so far our command line processing needs haven't been enough to justify a dependency for processing flags. However, a couple of things may change that consideration:
- rocsp-tool has a variety of subcommands (#6360) and we need a good way to make sure the documentation is up to date and the acceptable arg formats are consistent.
- boulder is now a single binary, dispatched by symlinking it with different names and executing it under various names depending on desired behavior. This requires an extra
link.shstep in our build, and is a little obscure. It would be nice to migrate to a subcommand style for invoking the various boulder services.
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
Review rocsp-tool and issue #6360 to understand its subcommands and documentation needs. Then inspect the current link.sh and symlink-based dispatch for the Boulder services. Done would require an agreed command-line parsing and invocation design that addresses both concerns, rather than a single obvious edit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100