User story #5449
closed
Make environment variables accessible as parameter in all Techniques
Added by Nicolas CHARLES about 10 years ago.
Updated over 9 years ago.
Description
The Rudder variable are replaced by Rudder in the Tehcnique
However, it is agnostic of the ncf, so it cannot replace it there
We could greatly benefit from having an easy solution to gather the env variable from the node and use them directly
A first idea is to use a module that would read the env variables, but in a standart technique, we would have no proof that it is run first (unless in system technique)
so let's start, for a poc, with a bundle common
ok, it's been decided to use ${node.env[ENV]} notation
- Subject changed from Environment variable defined with Rudder special variable ${rudder.node.end.xxx} cannot be used within ncf to Give access to the node system variable via ${node.env[ENV]}
- Target version changed from 140 to 3.0.0~beta1
- Status changed from New to Discussion
- Status changed from Discussion to 12
- Status changed from 12 to Pending release
- Category changed from System integration to 14
- Subject changed from Give access to the node system variable via ${node.env[ENV]} to Make environment variabla accessible as parameter in all Techniques
- Subject changed from Make environment variabla accessible as parameter in all Techniques to Make environment variables accessible as parameter in all Techniques
- Project changed from Rudder to 24
- Category deleted (
14)
- 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.
- Project changed from 24 to Rudder
- Category set to Techniques
Also available in: Atom
PDF
Updated by 
Updated by Matthieu CERDA 
Updated by Jonathan CLARKE 
Updated by 
Updated by