Project

General

Profile

Actions
Copy link

User story #3848

closed

Technique "Generic Variable definition": Allow empty values

User story #3848: Technique "Generic Variable definition": Allow empty values

Added by Olivier Mauras over 12 years ago. Updated over 10 years ago.

Status:
Released
Priority:
2
Assignee:
Vincent MEMBRÉ
Category:
Techniques
Target version:
2.6.11
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Use case:
content of a file enforced - default for all groups:
toto
tata
${generic_variable_definition.GROUP1_ONLY}
${generic_variable_definition.GROUP2_ONLY}
${generic_variable_definition.GROUP3_ONLY}

Default Generic CFEngine variable definition contains:
GROUP1_ONLY=""
GROUP2_ONLY=""
GROUP3_ONLY=""

group1 Generic CFEngine variable definition contains:
GROUP1_ONLY="tutu"

group2 Generic CFEngine variable definition contains:
GROUP2_ONLY="tztz"

and so on...

This gives a better flexibility in the rules applied to group. If you have a group that contains all your nodes on which you apply the default variables definition, you can just apply per group variables definition with lower priority while still using only one "content file enforcement".

Subtasks 1 (0 open — 1 closed)

User story #4469: Allow empty variable and make them overridable in generic variable techniquesReleasedJonathan CLARKEActions

Updated by Vincent MEMBRÉ over 12 years ago Actions
Copy link
 #2

  • Assignee set to Matthieu CERDA

I don't know if we have to handle the empty values in genericVariable technique, I think we forced people to add a value.

Maybe we should add a checkbox to handle empty values ?

A workaround for now, would be to use parameter with an empty value (need to validate that this is correctly working, but it's worth trying)

Jon, Matthieu, Nico, what do you think of handling empty variables in that Technique ?

Updated by Jonathan CLARKE over 12 years ago Actions
Copy link
 #3

  • Status changed from New to Discussion
  • Assignee changed from Matthieu CERDA to Jonathan CLARKE

Updated by Vincent MEMBRÉ almost 12 years ago Actions
Copy link
 #4

  • Assignee changed from Jonathan CLARKE to Vincent MEMBRÉ
  • Priority changed from N/A to 2
  • Target version set to 2.6.11

A pull request has been openend by Olivier: https://github.com/Normation/rudder-techniques/pull/168

I'll rebase it on 2.6 branch!

Updated by Vincent MEMBRÉ almost 12 years ago Actions
Copy link
 #5

  • Target version changed from 2.6.11 to 2.6.12

Updated by Vincent MEMBRÉ almost 12 years ago Actions
Copy link
 #6

  • Target version changed from 2.6.12 to 2.6.11

Updated by Vincent MEMBRÉ almost 12 years ago Actions
Copy link
 #7

  • Subject changed from Technique enhancement proposal: Allow empty values in generic variables technique to Technique "Generic Variable definition": Allow empty values

Updated by Vincent MEMBRÉ almost 12 years ago Actions
Copy link
 #8

  • Status changed from Discussion to 12

Updated by Vincent MEMBRÉ almost 12 years ago Actions
Copy link
 #9

  • Status changed from 12 to Pending release

Updated by Vincent MEMBRÉ almost 12 years ago Actions
Copy link
 #10

  • Project changed from Rudder to 24
  • Category deleted (Techniques)

Updated by Vincent MEMBRÉ almost 12 years ago Actions
Copy link
 #11

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.6.11, which was released today.
Check out:

Updated by Benoît PECCATTE over 10 years ago Actions
Copy link
 #12

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

Also available in: PDF Atom