The scripts are already provided in caucase-eggs part, there is no reason to
duplicate them here, so drop this entry.

/reviewed-on !579

Frontend operator shall have easy access to information about rejected
slaves, possibly the best in the JSON file.

Also the keys for the human readable information are slave's titles, not
references.

The information is published via hand crafted HTTPS endpoint.

Note: The SSL certificate is generated manually. Existing caucase is special
      for KeDiFa, this is another step to move all generated certificates (or
      otherwise self-signed) to internal, full automatic caucase.

/reviewed-on nexedi/slapos!580

We'll add monitoring to NEO so some parts are also moved there from ERP5.

As apache-ca-certificate field is not implemented for caddy, inform how to
obtain required functionality.

ssl_ca_crt is still supported and needed in the UI, so put it back with
DEPRECATED information.

/reviewed-by: TrustMe

  Missing update from previous commits

branch 1.0 is pinning the following repositories:
 * erp5
 * vifib
 * wendelin
 * wendelin.core
 * neoppod-repository

For resiliency, it's better to pin the repositories (we want exactly the
same software on runner0 and runner1). If people wants to develop inside
one of those repositories, they will clone it inside srv/runner/project
directory and this will be sync on runner1.

/reviewed-on nexedi/slapos!576

Rename was missing in buildout.hash.cfg

/reviewed-on nexedi/slapos!575

In "caddy-frontend: Implement KeDiFa SSL information" the certificates were
dropped from the schema, but still internally supported. This lead to missing
UI fields for still supported parameters.

Reintroduced them with OBSOLETE mark.

/reviewed-on nexedi/slapos!574

nginx-push-stream-module still it prevents from compiling nginx.

/reviewed-on nexedi/slapos!573

It is ready when all on-watch processes are not EXITED.

This reverts commit 83e9bd45

"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 nexedi/slapos!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.

[mock](https://docs.python.org/3/library/unittest.mock.html) and [responses](https://github.com/getsentry/responses).

/reviewed-on nexedi/slapos!568

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.