Project

General

Profile

Actions
Copy link

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
Assignee:
Vincent MEMBRÉ
Target version:
5.0-1.0
Pull Request:
https://github.com/Normation/rudder-p...
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 open — 2 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
Copy link
 #1

Updated by Alexis Mousset almost 6 years ago

  • Category set to Web - Config management
Actions
Copy link
 #2

Updated by François ARMAND almost 6 years ago

Actions
Copy link
 #3

Updated by François ARMAND almost 6 years ago

Actions
Copy link
 #4

Updated by François ARMAND almost 6 years ago

Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 5 years ago

  • Project changed from Rudder to 58
  • Category deleted (Web - Config management)
  • Target version set to 445
Actions
Copy link
 #6

Updated by François ARMAND over 5 years ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions
Copy link
 #7

Updated by François ARMAND over 5 years ago

  • Related to Architecture #13396: We need to be able to decide what workflow to use based on the change request added
Actions
Copy link
 #10

Updated by François ARMAND over 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder-plugins/pull/99
Actions
Copy link
 #11

Updated by François ARMAND over 5 years ago

For information, the related PR is just to set up all the backend infrastructure to be able to have the feature.

We will do an other one to create the UI and let the user actually choose groups.

Actions
Copy link
 #12

Updated by François ARMAND over 5 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ over 5 years ago

  • Project changed from 58 to Change validation
  • Target version changed from 445 to 5.0-1.0
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ about 4 years ago

  • Status changed from Pending release to Released
Actions
Copy link

Also available in: Atom PDF