Project

General

Profile

User story #12194

Target groups for the Validation Workflow

Added by Alexandre BRIANCEAU 9 months ago. Updated about 2 months ago.

Status:
Pending release
Priority:
N/A
Target version:
Suggestion strength:
Want - This would make my life a lot easier but I can manage without
User visibility:
Effort required:

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

Related to Change validation - Architecture #12905: Create validation workflows pluginsPending release
Related to Rudder - Architecture #13396: We need to be able to decide what workflow to use based on the change requestReleased

Associated revisions

Revision f6f45e3d (diff)
Added by François ARMAND 3 months ago

Fixes #12194: Target groups for the Validation Workflow

Revision 589e6445 (diff)
Added by François ARMAND 3 months ago

Fixes #12194: Target groups for the Validation Workflow

History

#1 Updated by Alexis MOUSSET 6 months ago

  • Category set to Web - Config management

#2 Updated by François ARMAND 5 months ago

#3 Updated by François ARMAND 5 months ago

#4 Updated by François ARMAND 5 months ago

#5 Updated by Vincent MEMBRÉ 4 months ago

  • Project changed from Rudder to 58
  • Category deleted (Web - Config management)
  • Target version set to 445

#6 Updated by François ARMAND 3 months ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND

#7 Updated by François ARMAND 3 months ago

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

#10 Updated by François ARMAND 3 months 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

#11 Updated by François ARMAND 3 months 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.

#12 Updated by François ARMAND 3 months ago

  • Status changed from Pending technical review to Pending release

#14 Updated by Vincent MEMBRÉ about 2 months ago

  • Project changed from 58 to Change validation
  • Target version changed from 445 to 5.0-1.0

Also available in: Atom PDF