Project

General

Profile

Actions

User story #12194

closed

Target groups for the Validation Workflow

Added by Alexandre BRIANCEAU about 6 years ago. Updated about 4 years ago.

Status:
Released
Priority:
N/A
Target version:
UX impact:
Suggestion strength:
Want - This would make my life a lot easier but I can manage without
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Context: being able to enable change request feature only on specific groups (eg: production nodes, security rules, etc.)

Description:
Currently, the Validation Workflow feature can be activated as an option and is applied to the entire Rudder server.

The main objective of this functionality is to secure the deployment of a change. This global application is not necessarily desired in some cases, for example it may be desirable to apply this security only on certain rules or sensitive/critical groups.

Expected results:
  • The option to apply the Validation Workflow functionality must include additional UI elements to restrict its application to certain groups/criteria.
  • Eventually we should be able to have the result of the criteria to limit the risk of erroneous criteria.
  • Eventually we should be able to distinguish in the Rudder UI an element requiring validation.

Related issues 2 (0 open2 closed)

Related to Change validation - Architecture #12905: Create validation workflows pluginsReleasedFrançois ARMANDActions
Related to Rudder - Architecture #13396: We need to be able to decide what workflow to use based on the change requestReleasedFrançois ARMANDActions
Actions

Also available in: Atom PDF