Actions
Bug #5801
closedUser story #5225: Allow to use environment variable from node inventory in directive rudder variables
Remove ${rudder.node.env.SOME_VARIABLE} parameter
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
#5225 was superseeded by #5449, so now, aside from having access to EVERY inventory parameters in an unified way, it does not make sense to keep ONLY environement variable and make things really muddy.
==> keep the logic to have the inventory information in the backend, but remove the entry point for ${rudder.node.env.SOME_VARIABLE} replacement.
Updated by François ARMAND about 10 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/663
(trivial) PR is here: https://github.com/Normation/rudder/pull/663
Updated by François ARMAND almost 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 92df1bff83ec4d11bd9d8aeed79eda907fbc09f0.
Updated by Vincent MEMBRÉ almost 10 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/
Actions