Mirrors/unleash.unleash
1
0
Fork 0
mirror of https://github.com/Unleash/unleash.git synced 2025-07-31 13:47:02 +02:00
Code Issues Projects Releases Wiki Activity

docs: environment change requests (#9648)

Browse Source
This commit is contained in:
Mateusz Kwasniewski 2025-04-03 12:25:23 +02:00 committed by GitHub
parent 3447b03e1c
commit 605ab54ae2
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 23 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
website/docs/reference/change-requests.mdx
View File

@ -16,7 +16,7 @@ Change requests allow you to require an additional approval step before any chan
Change requests also allow you to group changes and [apply them at a specific point in time](#scheduled-change-requests).
Change requests can be enabled on a per-project and per-environment basis. This allows you to differentiate your configurations across different environments, such as production and development.
Change requests can be enabled for a specific environment within a project, or configured globally for an environment across all projects. This allows you to differentiate your configurations across different environments, such as production and development.
You can require up to 10 approvals for a change request.
@ -104,6 +104,25 @@ While change requests are environment-specific, project segments are not. For th
Only Admin users can bypass the change request process for project segments through API calls.
## Environment-level change requests
:::note Availability
**Plan**: [Enterprise](https://www.getunleash.io/pricing) | **Version**: `6.10+`
:::
You can preconfigure change request requirements at the environment level. When configured, all new projects automatically inherit these approval requirements for the specified environments.
You can use environment-level change requests in two ways:
* **As defaults**: Set default approvals per environment, but allow project [Owners](/reference/rbac#projects#predefined-roles) and users with [project update permissions](/reference/rbac#projects) to override the defaults within their projects.
* **As enforced requirements**: Set mandatory approvals for a given environment across all projects. To fully enforce this in a project, ensure that the project has no Owner or users with project update permissions—this prevents any change request modifications at the project level.
You can predefine environment-level change requests when creating or editing an environment in **Configure > Environments**.
![Environment-level change requests](/img/environment-level-change-requests.png)
## Change request preview
To verify a change request, you can preview the changes in [Playground](/reference/playground) by clicking **Preview changes**. You can adjust [Unleash context](/reference/playground#the-unleash-context), but the project and environment remain fixed as they are determined by the change request.

BIN
website/static/img/environment-level-change-requests.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 264 KiB