Hi Dave.
On 31.03.20 09:24, Dave Cottlehuber wrote:
hi all,
Our main haproxy.conf has practically become sentient... it's reached the
point where the number of url redirects and similar incantations is very
hard to reason about, and certainly not test or validate, until it's
shipped. In fact I deploy to a "B" cluster node, and verify most changes
on a spare production node. This is not always possible to ensure that
existing acls and url redirects aren't broken by the changes.
For example:
https://%[hdr(host)]%[url,regsub(/$,)] ...
didn't do what the person who deployed it thinks it does - easy enough to
fix. How could we have tested this locally before committing it?
Is there any easy-ish way to try out these rules, almost like you
could in a REPL?
Once we've written them, and committed them to our ansible repos, is there
any way to unit test the whole config, to avoid regressions?
90% of these commits relate to remapping and redirecting urls from patterns.
Please can you tell us which version of HAProxy and some more details from the
config.
Maybe you can split the redirects, for example can you use a map for the host
part.
A+
Dave
Regards
Aleks
