Project

General

Profile

Actions

User story #9063

closed

Add support for a rudder_version check in list-compatible-input and policy loading

Added by Alexis Mousset about 8 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Generic methods
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

We need to:

  • Find the Rudder version
  • Change list-compatible input to be able to filter on it
  • Change ncf python script to extract it too
  • Change documentation scripts to be able to display it

The behavior will be:

agent if feature, version support dry-run support
Rudder <=3.1.13, <= 3.2.6 no no
Rudder >3.1.13, >3.2.6 yes no
Rudder >= 4.0 yes yes
CFEngine 3.6 no no
CFEngine 3.7 if version only no
CFEngine >= 3.9 yes yes

The behavior will be:

agent_version in the file r@udder_version@ in the file agent version in the agent case outcome
no no * no restriction
yes no no not a Rudder agent, standard CFEngine comparison use CFEngine version
yes no yes it is a Rudder agent but no restriction, standard CFEngine comparison use CFEngine version
no yes no it is not a Rudder agent use CFEngine version
no yes yes it is a Rudder agent, and we have a restriction use Rudder version
yes yes no it is not a Rudder agent use CFEngine version
yes yes yes it is a Rudder agent, and we have a restriction use Rudder version

Subtasks 2 (0 open2 closed)

User story #9065: Use rudder_version in ncf scriptsRejectedAlexis MoussetActions
User story #9088: Call lis-compatible-inputs with rudder_version if presentRejectedAlexis MoussetActions

Related issues 2 (0 open2 closed)

Related to Rudder - User story #9062: Mark the correct version dependencies in dry-run testsReleasedNicolas CHARLESActions
Related to Rudder - User story #9041: Change system promises to call list-compatible-inputs with capabilities fileReleasedAlexis Mousset2016-09-14Actions
Actions

Also available in: Atom PDF