User story #5225
closed
Allow to use environment variable from node inventory in directive rudder variables
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
Updated by François ARMAND almost 10 years ago
- 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 9 years ago
- 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 9 years ago
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
Updated by François ARMAND over 9 years ago
- Status changed from 10 to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
Ready for technical review.
Updated by François ARMAND over 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 5aff0242e9a7356250ad99ff50735e6aa3b47f4e.
Updated by Nicolas CHARLES over 9 years ago
Applied in changeset 9c2cd7729e78299865deedf4faa7cb7952bffa21.
Updated by François ARMAND over 9 years ago
It is to be noted that that feature does not impact the NodeConfigurationCache logic because variable interpolation is done BEFORE the cache check.
Updated by Matthieu CERDA over 9 years ago
- Target version changed from 140 to 3.0.0~beta1
Updated by Vincent MEMBRÉ over 9 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0~beta1 which was release on 01/12/2014.
- Announcement
- Changelog
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by François ARMAND over 9 years ago
- Tracker changed from Enhancement to User story
- Parent task deleted (
#3112)