RelEng: Build hpke_keygen tool and upload as release artifact
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 70
- Forks
- 16
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 30
Description
We will need to instruct subscribers on how to manage the HPKE keypair for their collector, at least until managed DAP collector services are available. This requires DAP-specific tooling, as DAP defines its own HpkeConfig serialization format. We should add another GHA workflow that runs upon release, builds the hpke_keygen tool in release mode, and uploads it as a release asset. This would let us simplify instructions, by not requiring subscribers to install Git and Rust first.
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 locating the existing Rust hpke_keygen tool and the repository's GitHub Actions workflows. Read how releases are triggered and how the tool is built in release mode, then add a release workflow that uploads the built tool as a release asset. Done means a release produces an accessible hpke_keygen artifact for subscribers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100