Project

General

Profile

Actions
Copy link

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.

Status:
Released
Priority:
N/A
Assignee:
-
Category:
Techniques
Target version:
3.0.0~beta1
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

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

Subtasks 2 (0 open — 2 closed)

User story #5643: Implement node variable acces via ${node.env[ENV]}ReleasedJonathan CLARKE2014-10-14Actions
Bug #5873: Non-escaped quotes in environment-variables.cf cause CFEngine parsing errorReleasedNicolas CHARLES2014-11-29Actions

Related issues 3 (0 open — 3 closed)

Related to Rudder - User story #5225: Allow to use environment variable from node inventory in directive rudder variablesReleasedNicolas CHARLES2014-07-07Actions
Related to Rudder - User story #4670: Allows inventories to be augmented by the user with custom propertiesReleasedFrançois ARMANDActions
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
Copy link
 #1

Updated by Nicolas CHARLES about 10 years ago

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

Actions
Copy link
 #3

Updated by Nicolas CHARLES about 10 years ago

Actions
Copy link
 #4

Updated by Nicolas CHARLES about 10 years ago

ok, it's been decided to use ${node.env[ENV]} notation

Actions
Copy link
 #5

Updated by Nicolas CHARLES about 10 years ago

  • 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]}
Actions
Copy link
 #6

Updated by Matthieu CERDA about 10 years ago

  • Target version changed from 140 to 3.0.0~beta1
Actions
Copy link
 #7

Updated by Jonathan CLARKE almost 10 years ago

  • Status changed from New to Discussion
Actions
Copy link
 #8

Updated by Jonathan CLARKE almost 10 years ago

  • Status changed from Discussion to 12
Actions
Copy link
 #9

Updated by Jonathan CLARKE almost 10 years ago

  • Status changed from 12 to Pending release
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ almost 10 years ago

  • Category changed from System integration to 14
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ almost 10 years ago

  • Subject changed from Give access to the node system variable via ${node.env[ENV]} to Make environment variabla accessible as parameter in all Techniques
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ almost 10 years ago

  • Subject changed from Make environment variabla accessible as parameter in all Techniques to Make environment variables accessible as parameter in all Techniques
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ almost 10 years ago

  • Project changed from Rudder to 24
  • Category deleted (14)
Actions
Copy link
 #14

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.

Actions
Copy link
 #15

Updated by Benoît PECCATTE over 9 years ago

  • Project changed from 24 to Rudder
  • Category set to Techniques
Actions
Copy link

Also available in: Atom PDF