Project

General

Profile

Actions

Bug #6125

closed

We can define key-values on nodes, but we can't use it in the directives

Added by Nicolas CHARLES almost 10 years ago. Updated over 8 years ago.

Status:
Rejected
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

We introduced key-values that can be attached to Nodes, but we can't use these value in the generated promises, which is kind of a sad :(


Related issues 3 (0 open3 closed)

Related to Rudder - User story #3112: Allow to get informations from the node inventory to use them in Directives and ncf techniquesReleasedFrançois ARMANDActions
Related to Rudder - User story #8549: User Management: Support for rudder variables in password fieldRejectedActions
Is duplicate of Rudder - User story #6733: Allow Node properties to be used in directives and ncf techniquesReleased2016-07-20Actions
Actions #1

Updated by François ARMAND almost 10 years ago

Yes, that seems to be an overlooked. It could be done in the same way as ${rudder.node.hostname/etc} works.
But then, I don't know how to use them within ncf-builder.

So, do we want to add a ${rudder.node.prop.FOO} (that will be changed to "bar" if such FOO property is defined on node) ?

See #5225 that expose the problems, the solution used for environment variable in #5449, and the general user story in #3112.

Actions #2

Updated by François ARMAND almost 10 years ago

Note that the situation is a little better than environment variable because at least, our properties are clearly defined on the node on Rudder side, and so we don't have to wonder what value we want to use at run time - it's the value that was available when the promise was generated.

Actions #3

Updated by François ARMAND almost 10 years ago

  • Target version changed from 3.0.0 to 3.1.0~beta1
Actions #4

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.1.0~beta1 to 3.1.0~rc1
Actions #5

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.1.0~rc1 to 3.1.0
Actions #6

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.1.0 to 3.1.1
Actions #7

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.1.1 to 3.1.2
Actions #8

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 3.1.2 to 3.1.3
Actions #9

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 3.1.3 to 3.1.4
Actions #10

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 3.1.4 to 3.1.5
Actions #11

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 3.1.5 to 3.1.6
Actions #12

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 3.1.6 to 3.1.7
Actions #13

Updated by Janos Mattyasovszky almost 9 years ago

+1

Actions #14

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.7 to 3.1.8
Actions #15

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.8 to 3.1.9
Actions #16

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.9 to 3.1.10
Actions #17

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.10 to 3.1.11
Actions #18

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.11 to 3.1.12
Actions #19

Updated by François ARMAND over 8 years ago

  • Related to User story #8549: User Management: Support for rudder variables in password field added
Actions #20

Updated by François ARMAND over 8 years ago

  • Status changed from New to Rejected

Closing this one as duplicate of #6733 (because #6733 contains more information)

Actions #21

Updated by François ARMAND over 8 years ago

  • Is duplicate of User story #6733: Allow Node properties to be used in directives and ncf techniques added
Actions

Also available in: Atom PDF