Project

General

Profile

User story #751

Test the typed variables in Directives on a test node

Added by Nicolas CHARLES almost 6 years ago. Updated about 2 months ago.

Status:
Rejected
Priority:
5
Category:
Web - Config management
Start date:
2011-02-01
Due date:
% Done:

0%

Pull Request:

Description

We need to be able to validate the variables that have been typed in Directives for real, not by just verifying their type.

A good way would be to have a "fake" node that would just have the common and newly created Directive, write the promises and validate them with cf-promises (enterprise and community?) that everythings correct, before saving.


Related issues

Related to Rudder - User story #5641: Make the agent policies update a state machine with integrity check New 2014-10-14

History

#1 Updated by François ARMAND about 5 years ago

  • Target version set to 24

#3 Updated by Jonathan CLARKE over 4 years ago

  • Target version changed from 24 to Ideas (not version specific)

#4 Updated by François ARMAND almost 4 years ago

  • Status changed from New to Discussion
  • Assignee set to Nicolas CHARLES

Don't wa actually validate with cf-promises today ?

#5 Updated by Nicolas CHARLES almost 4 years ago

Currently, the only testts we are doing is when deploying policies; which can be a long time after someone defined a directive (the time for the change to be accepted)
We should be able to immediately check that the directive created is valid (proper variable), and to do so, we should "deploy" it on a dummy node, where we would only cf-promises it

#6 Updated by Matthieu CERDA over 1 year ago

  • Subject changed from Tester les variables saisie à la creation d'une PI avec une node de test to Test the typed variables in Directives on a test node
  • Description updated (diff)

#8 Updated by Matthieu CERDA over 1 year ago

Nicolas, can you clarify here what is the difference between the current way we validate promises on nodes before deployment ? I feel this description is quite close to what we do already today :)

#9 Updated by Benoît PECCATTE about 2 months ago

  • Status changed from Discussion to Rejected

Having a test node could never cover all possible values like calling cf-promises never cover all possible values.

This is not possible without running the agent itself.
The only thing that is better than what we do today is checking directly on the node, which is what is proposed by #5641.

#10 Updated by Benoît PECCATTE about 2 months ago

  • Related to User story #5641: Make the agent policies update a state machine with integrity check added

Also available in: Atom PDF