Project

General

Profile

Actions

User story #5449

closed

Make environment variables accessible as parameter in all Techniques

Added by Nicolas CHARLES over 6 years ago. Updated about 6 years ago.

Status:
Released
Priority:
N/A
Assignee:
-
Category:
Techniques
Target version:
Suggestion strength:
User visibility:
Effort required:

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 open2 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

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 #1

Updated by Nicolas CHARLES over 6 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 #3

Updated by Nicolas CHARLES over 6 years ago

Actions #4

Updated by Nicolas CHARLES over 6 years ago

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

Actions #5

Updated by Nicolas CHARLES over 6 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 #6

Updated by Matthieu CERDA over 6 years ago

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

Updated by Jonathan CLARKE over 6 years ago

  • Status changed from New to Discussion
Actions #8

Updated by Jonathan CLARKE over 6 years ago

  • Status changed from Discussion to 12
Actions #9

Updated by Jonathan CLARKE over 6 years ago

  • Status changed from 12 to Pending release
Actions #10

Updated by Vincent MEMBRÉ over 6 years ago

  • Category changed from System integration to 14
Actions #11

Updated by Vincent MEMBRÉ over 6 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 #12

Updated by Vincent MEMBRÉ over 6 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 #13

Updated by Vincent MEMBRÉ over 6 years ago

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

Updated by Vincent MEMBRÉ over 6 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 #15

Updated by Benoît PECCATTE about 6 years ago

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

Also available in: Atom PDF