Change Requests & Reviews
Treat cluster changes like pull requests — propose, review, comment, approve, then merge.
Why Change Requests?
For Nexuses with many editors, you want review before changes go live. Change Requests give you a Git-style workflow over your API clusters and shared resources.
Lifecycle
- Editor opens a CR with a diff (added/removed/modified endpoints, variables, scripts).
- Reviewers see it in their inbox in real time.
- Comments thread per change line.
- Approve → merged into the live cluster. Reject → CR closed with reason.
Roles
| Role | Can open CR | Can approve |
|---|---|---|
| Owner | Yes | Yes |
| Admin | Yes | Yes |
| Editor | Yes | No (peer review only) |
| Viewer | No | No (can comment) |