FlowFuse / FlowFuse/flowfuse

Review-Based Pipeline Execution

Open
#3,139 0 comments 0 reactions 0 assignees View on GitHub
epic needs-triage sales request
Dominant language
JavaScript
Stars
400
Forks
89
Avg merge
1d 20h
Merged PRs (30d)
149

Description

## Description
This feature serves as an alternative to implementing more granular Role-Based Access Control (RBAC) roles (https://github.com/FlowFuse/flowfuse/issues/3093). It introduces a safeguard similar to the branch protection mechanism commonly used in Git workflows. In this setup, the Productive Instance Node-RED (akin to the main branch in Git) is configured as a protected environment. A pipeline destined for this environment must first be reviewed and approved by a designated reviewer from the team, who possesses the necessary Owner permissions. This review step is critical to maintain code integrity and system stability by ensuring that only verified and sanctioned changes are implemented in the productive instance.

### Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate
```[tasklist]
### Stories
- [ ] https://github.com/FlowFuse/flowfuse/issues/277
- [ ] https://github.com/FlowFuse/flowfuse/issues/3488
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.