C
Circular Fish
Current Challenge:
  • When using Approval steps in Custom Stages, new pipeline executions automatically reject previous executions that are waiting for approval
  • Moving approvals to CD Stages (as currently suggested) requires individual approval for each service deployment, which is impractical for organizations with 50+ microservices
Feature Request:
We need a way to implement pipeline-level or global approvals that:
  1. Do NOT auto-reject previous pending executions when new executions start
  2. Allow a single approval to cover multiple service deployments within the same pipeline execution
  3. Maintain the approval workflow integrity without requiring 50+ individual approvals per release