Deploy hooks and outgoing webhooks per application

Open
  • Is something wrong?
#262 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
angular, typescript
Domain
api, backend, devops, security

Research direction

Read the M3.1 dependency and trace how applications queue deployments in the control plane, then inspect the web UI's Application → Webhooks section. The issue calls for HMAC-signed deployment triggers and signed deploy.succeeded and deploy.failed events; confirm the acceptance criteria cover forged and replayed requests. Done means valid triggers queue deployments, invalid or replayed triggers are refused, and outgoing events are signed.

Written by the indexing model from the issue text.

Description

priority:P2 security-review task track:control-plane track:web
Track

C: control plane, W: web UI

Scope
  • Application → Webhooks section (preview): an HMAC-signed URL to trigger a deployment from CI, and outgoing events (deploy.succeeded, deploy.failed).
Acceptance criteria

A correctly signed call queues a deployment, a forged or replayed one is refused; outgoing events are signed.

Depends on

M3.1

Dominant language
TypeScript
Stars
2
Forks
1
Avg merge
7h 17m
Merged PRs (30d)
197

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from shipkeepdev/shipkeep

All issues in shipkeepdev/shipkeep

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.