Approvals for protected environments

Open
  • Is something wrong?
#261 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, docker, typescript
Domain
backend, devops, frontend, security

Research direction

Start by locating the Application → Approvals section in the web UI and the deployment and secret-change flows in the control plane. Read how protected environments, admin permissions, and audit transactions are currently handled. The work is done when protected-environment deployments remain pending until an eligible admin approves them, and approval or refusal is audited in the same transaction; the required approver count and self-approval switch also need implementation.

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 → Approvals section (preview): deployments and secret changes in a protected environment wait for an admin's approval.
  • Approvers, required count, self-approval switch.
Acceptance criteria

A deploy to a protected environment stays pending until approved by another admin; approval and refusal are audited in the same transaction.

Depends on

—

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.