4 Commits

Author	SHA1	Message	Date
Willy Tarreau	f2e44d4e87	REGTESTS: add more complex check conditions to check_conditions.vtc ... Now that we support logic expressions, variables and parenthesis, let's add a few more tests to check_conditions.vtc. The tests are conditionned by the version being at least 2.5-dev2 so that it will not cause failures during a possible later bisect session or if backported. The test verifies that exported variables are seen, that operators precedence works as expected, that parenthesis work at least through two levels, that an empty condition is false while a negative number is true, and that extraneous chars in an expression, or unfinished strings are properly caught.	2021-07-17 11:01:47 +02:00
Willy Tarreau	b333db3fd2	REGTEST: make check_condition.vtc fail as soon as possible ... The test consists in a sequence of shell commands, but the shell is not necessarily started with strict errors enabled, so only the last command provides the verdict. Let's add "set -e" to make it fail on the first test that fails.	2021-07-17 10:56:32 +02:00
Tim Duesterhus	5efc48dcf1	REGTESTS: Replace REQUIRE_VERSION=2.5 with 'haproxy -cc' ... This is safe, because running `haproxy -cc 'version_atleast(2.5-dev0)'` on HAProxy 2.4 will also result in an exit code of 1.	2021-06-17 14:59:55 +02:00
Maximilian Mader	fc0cceb08a	MINOR: haproxy: Add -cc argument ... This patch adds the `-cc` (check condition) argument to evaluate conditions on startup and return the result as the exit code. As an example this can be used to easily check HAProxy's version in scripts: haproxy -cc 'version_atleast(2.4)' This resolves GitHub issue #1246. Co-authored-by: Tim Duesterhus <tim@bastelstu.be>	2021-06-08 11:17:19 +02:00