"openssl ca" is keeping track of all generated certificates in its DB.
If we try to regenerate a certificate that was already generated,
openssl ca fails with :

ERROR:There is already a certificate for /C=XX/ST=(State,)/O=Company/CN=ca-shellinabox/emailAddress=xx@example.com

Changing "unique_subject" to no removes this ERROR.

/reviewed-on !556

Before normalize_ae_gzip was 0, and better keep it this way as it is
suspected root problem of incorrectly varianted cache depending on
client Accept-Encoding.

This reverts commit 8251f3dd.

1.4.23 is not available on pypi yet, causing all involved software releases
to fail instanciating, breaking all tests.
Feel free to reapply once the version is actually released.

Since we moved to MariaDB 10.3, that's actually already the case
because of --plugin-maturity=gamma

mock is only a test dependency for zobduri

https://github.com/getsentry/responses A utility for mocking out the
Python Requests library.

https://pypi.org/project/mock/ which is a backport of
https://docs.python.org/3/library/unittest.mock.html

Instead of expensive and long checking of the configuration during promise run
read last stored state.

This decouples configuration validation calculation from promise check. The
validation information is updated often (on each configuration change, on each
reload, etc) and every 2 hours.

Validation happens on each configuration change, but for sure it is checked
each 2 hours.

State of configuration is calculated in separate script.

Order of files does not matter for the assertion.

Tests need to open xz files for checking.

It's interesting what appears in cron entries, as they are important for proper
partition usage.

Always work from the slave_dir path for extensibility and allow no ignore
paths if caller does not need to ignore anything.

Ignore path's shall be relative to checked directory.

Move files from var/log/trafficserver/*old to
srv/backup/logrotate/trafficserver, xz them and clean files older than a
year.

As some tools are not configurable with logrotate provide a script to
"rotate" files generated by those tools.
This script more or less follows logrotate behaviour:

 * moves rotated files to logrotate directory
 * compresses them with xz
 * have to be configured to keep only files for some days

Roll logs each 24h, as it would be expected.

  Upper limits makes harder deploy larger systems

Stderr to null redirection happened in the wrong place.

Promises will fail with stderr filled, and it can be such if sha256sum emits
error messages, so just discard them.

Some arguments needs Caddy process restart, so implement it with
hash-files and also inform the master partition requester about parameters
which will result with process restart.

Kedifa partition was missing monitoring at all, so add it and monitor kedifa
and exposer ip and port.

Partition running caddy was missing monitoring for exposer, so add it.

Use unreal address to avoid any tries for network connectivity.

Kedifa requires some time to process new slave, and during that time the key
download URL is not available, but as it is required for proper mapping file,
use some url to mimic it.