Project

General

Profile

Actions

User story #10577

closed

Choose node behaviour before accepting it

Added by Rémi Verchère almost 7 years ago. Updated almost 5 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Config management
UX impact:
Suggestion strength:
Want - This would make my life a lot easier but I can manage without
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Name check:
Fix check:
Regression:

Description

When I accept a new node, I cannot choose the audit/enforce mode before acceptance. It uses the global settings.

I'd like to do the following:
- Set up global config to "enforce", to be sure all my registered nodes are OK
- Insert new node in "audit" mode, to make it auditable before settings/forcing all rules

So, can we make audit mode configurable before adding new nodes?

Actions #1

Updated by Alexis Mousset almost 7 years ago

  • Category set to Web - Config management
  • Target version set to 4.1.2
Actions #2

Updated by François ARMAND almost 7 years ago

Thanks for reporting, you are right that we should be able to config the node parameter before accepting it. Audit/enforce is an example, but any node parameter (run interval, node property, etc) should be configurable before acceptation.

For you special use case, a workaround can be to just inverse the global/override mode: by default (global), you could use "audit", so that new unstested things (node or other) don't change anything. And when you are confident about the behavior, switch the item to enforce.

A general, not at all (but really not at all) user friendly, workaround is to edit the LDAP database to add an entry for the not-yet-accepted node under "ou=Nodes,cn=rudder-configuration" and set the value to what is wanted. All node properties can be configured like that, but it requires some love of LDAP, and internal knowledge of the serialisation format of each node parameter (it can be derived from other nodes, but...)

Actions #3

Updated by Rémi Verchère almost 7 years ago

François ARMAND wrote:

A general, not at all (but really not at all) user friendly, workaround is to edit the LDAP database to add an entry for the not-yet-accepted node under "ou=Nodes,cn=rudder-configuration" and set the value to what is wanted. All node properties can be configured like that, but it requires some love of LDAP, and internal knowledge of the serialisation format of each node parameter (it can be derived from other nodes, but...)

Even if I love LDAP, I think the best workaround is having the global parameter set to "Audit", and then change each node to "Enforce" once I am confident ;)

Actions #4

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.1.2 to 4.1.3
Actions #5

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.1.3 to 4.1.4
Actions #6

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.1.4 to 4.1.5
Actions #7

Updated by Alexis Mousset almost 7 years ago

  • Target version changed from 4.1.5 to 4.1.6
Actions #8

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.6 to 4.1.7
Actions #9

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.7 to 4.1.8
Actions #10

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.8 to 4.1.9
Actions #11

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.9 to 4.1.10
Actions #12

Updated by Benoît PECCATTE about 6 years ago

  • Target version changed from 4.1.10 to Ideas (not version specific)
Actions #13

Updated by Alexis Mousset almost 5 years ago

  • Status changed from New to Rejected

We now have a "Set default settings value on node acceptation" configuration that allows having a global enforce mode and new nodes added in audit mode.

Actions

Also available in: Atom PDF