Project

General

Profile

Actions

Bug #15767

closed

cf-promise check (development policy check) must be *uncheked* by default

Added by François ARMAND over 5 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
N/A
Category:
Performance and scalability
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:

Description

It leads to suffer and pain for no reason.

Actions #1

Updated by François ARMAND over 5 years ago

  • Status changed from New to In progress
Actions #2

Updated by François ARMAND over 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/2473
Actions #3

Updated by Nicolas CHARLES over 5 years ago

Actually, for most common usages, it is really useful to have the policy generation check - it helps catch error when users are developping/migrating their own techniques/generic method, or when typos got in (like mismatched $() ${} )

For large production environnement (so when a test env is avaialable), it is indeed painful (but must be left for dev/test)

In the future, it will be checked on the node side. And it will be good

Actions #4

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from Pending technical review to Rejected
Actions

Also available in: Atom PDF