Project

General

Profile

Actions

User story #5225

closed

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

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

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
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 open3 closed)

User story #5236: Add a bulk load for NodeInventory informationReleasedNicolas CHARLES2014-07-07Actions
Bug #5801: Remove ${rudder.node.env.SOME_VARIABLE} parameterReleasedNicolas CHARLES2014-11-26Actions
Bug #5831: Remove tests on node.envReleasedFrançois ARMAND2014-11-26Actions

Related issues 3 (0 open3 closed)

Related to Rudder - User story #5278: Document allowed ${rudder.variable} in directive formResolvedActions
Related to Rudder - User story #5449: Make environment variables accessible as parameter in all TechniquesReleased2014-10-14Actions
Related to Rudder - User story #3112: Allow to get informations from the node inventory to use them in Directives and ncf techniquesReleasedFrançois ARMANDActions
Actions

Also available in: Atom PDF