4 Commits (1c6c356350c3d28d70b3f361e0b80db0ba37e15d)

Author	SHA1	Message	Date
Rick Elrod	19aeb4706d	[conditional] Remove support for bare variables (#74208) ... Change: - Variables used in ``when`` conditionals are no longer parsed and attempted to be converted to booleans. All non-empty strings are considered true (empty strings, false). Test Plan: - Updated existing tests - Added a bunch of new tests with various kinds of truthy/falsy values. Tickets: - Fixes #74134 Signed-off-by: Rick Elrod <rick@elrod.me>	4 years ago
Sloane Hertel	21cd24a0dd	improve conditional warnings (#57190) ... * Fix order for warning on templated conditionals Fix bare variable warnings when the variable is a boolean * changelog * Add tests for cases that should and should not give warnings If the behavior may change when the default behavior for CONDITIONAL_BARE_VARS becomes False there should be a warning. Boolean type conditionals will not change in behavior so don't warn. * oops, forgot to add files * typo	6 years ago
Matt Clay	5134ba95ca	Fix conditionals integration test. (#53583) ... * Fix inventory for conditionals test. * Remove extra groups from conditionals test.	6 years ago
Brian Coca	4a0fceaa3b	remove bare var handling in conditionals (#51030) ... * remove bare var handling in conditionals this makes top level and multilevel vars (dicts keys) behave the same it will require adding |bool for 'string comparissons' in indirect templates - added new tests to ensure uniform handling - switched to 'is' testing for status - changed warning to 'conditional' as 'when:' is not only place it gets triggered * updated to include toggle and deprecation * fix deprecated * updated tests to handle toggle * fixed typo and added note about the future	6 years ago