redhat-developer / redhat-developer/abbenay
feat(daemon): CLI flags for custom gRPC TLS cert/key/CA paths
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12
- Forks
- 7
- Avg merge
- 7h 7m
- Merged PRs (30d)
- 3
Description
Context
PR #63 adds --grpc-tls with auto-generated self-signed certs. Custom PEM paths exist only as @internal options for tests (certPath / keyPath / caPath). Production/container users who bring org-issued certificates have no CLI surface.
Flagged during review of PR #63: https://github.com/redhat-developer/abbenay/pull/63
Proposal
- Expose something like
--grpc-tls-cert,--grpc-tls-key,--grpc-tls-ca(names TBD) - Keep auto-gen as the default for
--grpc-tlswith no paths - Document usage in DEVELOPMENT.md / CONTAINER.md
References
- PR #63
- DR-029
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 by reviewing PR #63 and the daemon's existing internal certPath, keyPath, and caPath options to locate the current TLS configuration entry point. Define the CLI flag names and preserve auto-generation when --grpc-tls has no paths, then document the usage in DEVELOPMENT.md and CONTAINER.md; DR-029 provides additional context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, typescript
- Domain
- api, cli, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100