Bug #15767
closed
cf-promise check (development policy check) must be *uncheked* by default
Added by François ARMAND about 5 years ago.
Updated about 5 years ago.
Category:
Performance and scalability
Description
It leads to suffer and pain for no reason.
- Status changed from New to In progress
- 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
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
- Status changed from Pending technical review to Rejected
Also available in: Atom
PDF
Updated by 
Updated by