Install a repository and prove webhook delivery #12

Open
opened 2026-07-14 22:32:18 -04:00 by caleb-brown · 0 comments
Owner

What to build

A Temper Operator can create a Repository Installation, configure its webhook manually or with separately authorized assistance, and prove that authenticated Forgejo events reach the correct installation.

Acceptance criteria

  • An Operator can select an accessible repository and create one unique Repository Installation.
  • Temper generates and encrypts a repository-specific webhook secret and presents complete manual webhook instructions.
  • API-assisted webhook creation is offered only when the PAT has the additional required permission.
  • A signed test or live delivery changes the Repository Installation from awaiting webhook to ready and records only safe delivery metadata.
  • Invalid signatures, oversized payloads, unknown installations, and replayed delivery identifiers are rejected or deduplicated predictably.
  • Connection, repository, webhook, and readiness failures are distinct and show a corrective Operator action.
  • An end-to-end test proves manual onboarding and authenticated delivery without requiring repository-administration permission.

Blocked by

  • #11 — Connect and verify a Forgejo service identity
## What to build A Temper Operator can create a Repository Installation, configure its webhook manually or with separately authorized assistance, and prove that authenticated Forgejo events reach the correct installation. ## Acceptance criteria - [ ] An Operator can select an accessible repository and create one unique Repository Installation. - [ ] Temper generates and encrypts a repository-specific webhook secret and presents complete manual webhook instructions. - [ ] API-assisted webhook creation is offered only when the PAT has the additional required permission. - [ ] A signed test or live delivery changes the Repository Installation from awaiting webhook to ready and records only safe delivery metadata. - [ ] Invalid signatures, oversized payloads, unknown installations, and replayed delivery identifiers are rejected or deduplicated predictably. - [ ] Connection, repository, webhook, and readiness failures are distinct and show a corrective Operator action. - [ ] An end-to-end test proves manual onboarding and authenticated delivery without requiring repository-administration permission. ## Blocked by - [#11](https://git.caleb-brown.dev/caleb-brown/temper/issues/11) — Connect and verify a Forgejo service identity
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
caleb-brown/temper#12
No description provided.