User story #5225: Allow to use environment variable from node inventory in directive rudder variables - Rudder - Issue Tracker

Actions

Copy link

User story #5225

closed

Allow to use environment variable from node inventory in directive rudder variables

User story #5225: Allow to use environment variable from node inventory in directive rudder variables

Added by François ARMAND over 11 years ago. Updated almost 11 years ago.

Status:

Released

Priority:

N/A

Assignee:

Nicolas CHARLES

Category:

Web - Config management

Target version:

3.0.0~beta1

Pull Request:

UX impact:

Suggestion strength:

User visibility:

Effort required:

Name check:

Fix check:

Regression:

Description

In a directive, we are allowed to use rudder parametrized variable, see: http://www.rudder-project.org/foswiki/Development/ContextedVariables

We want to be able to access environment variable value from the node inventory as such variable, with the following semantic:

${rudder.node.env.SOME_VARIABLE} is replaced by:

- "" is the variable does not exist or is empty
- the value of SOME_VARIABLE, considered as a string, as reported in the inventory in the <VAL> tag for the <KEY>SOME_VARIABLE</KEY> tag of an <ENVS>.

For posterity: this ticket was implemented and removed during 3.0 cycle in favor of #5449. A more generic solution will be implemented in #3112

Subtasks 3 (0 open — 3 closed)

Related issues 3 (0 open — 3 closed)

Updated by François ARMAND over 11 years ago Actions
Copy link
#1

Pull Request set to https://github.com/Normation/rudder/pull/572

The pull request with all the logic & unit tests is here: https://github.com/Normation/rudder/pull/572

I would like to test what happens when a lot of nodes exists before merging that.

Updated by François ARMAND over 11 years ago Actions
Copy link
#2

Status changed from In progress to 10

The tests show that the performances are very lightly impacted by that addition, also meaning that adding any other inventory information is mostly free.

Updated by François ARMAND over 11 years ago Actions
Copy link
#3

Functionnal review agreed on the following points:

- syntax: ${rudder.node.env.ENVIRONMENT_VARIABLE_NAME},
- replaced by the value of the environment variable "ENVIRONMENT_VARIABLE_NAME",
- case sensitive,
- as known in the last inventory for the node,
- or "" if there is no variable with that name for that node

We now need to add information about allowed parameters in the directive screen, see: #5278