The consumer groups were cleaned so we have to replay
from the beginning :(

The good news is it should be faster as the data is already present.

Related to swh/infra/sysadm-environment#4739

Split the max query cost for authenticated and unauthenticated users

Related to swh/infra/sysadm-environment#4785

Related to swh/infra/sysadm-environment#4785

related to swh/infra/sysadm-environment#4785

Depends on swh/infra/ci-cd/swh-charts!30

Related to swh/infra/sysadm-environment#4785

Related to swh/infra/sysadm-environment#4785

It will be used by graphq >= 0.0.8.1 and later by the webapp

Related to swh/infra/sysadm-environment#4785

Refs. swh/infra/sysadm-environment#4792

Otherwise, helm install is not happy about non-quoted yes complaining about
that missing function.

Refs. swh/infra/sysadm-environment#4776

Otherwise, argocd complains about it being mistyped.

"one or more objects failed to apply, reason: "" is invalid: patch: Invalid
value... unrecognized type: string (retried 5 times)."

Refs. swh/infra/sysadm-environment#4776

By default, loader do not report their exceptions to sentry.

Refs. swh/infra/sysadm-environment#4776

Refs. swh/infra/sysadm-environment#4774

This reverts commit 1db6fa23.

- Declare the new configuration variables needed by the v0.0.7 version
- Add one more replicas to increase availability in case of node crash

Related to swh/infra/sysadm-environment#4765

Implement unit tests for the graphql descriptors.
Some changes were needed outside graphql in order to allow the generation
with the default values.

Related swh/infra/sysadm-environment#4765

Related to swh/infra/sysadm-environment#4765

Besides loader_git.

It's a temporary workaround. The targeted solution is to install the missing
cogs (filebeat) to push thos json logs instructions to logstash. That's been worked on.

When it will be ready, images will be rebuilt with the new pythonjsonlogger dependency
and this will be reverted.

Refs. swh/infra/sysadm-environment#4524

They are now all deployed in the gitlab registry.
And appVersion got bumped to 2.

Actually updated using the app_manager script:
```
cd swh-apps
./scripts/app_manager.py update-versions --applications-filepath ../swh-charts/values-swh-application-versions.yaml --chart-filepath ../swh-charts/swh/Chart.yaml
Missing or inconsistent information for <swh_provenance_server>
Missing or inconsistent information for <swh_provenance_client>
```

Refs. swh/infra/sysadm-environment#4524

Refs. swh/infra/sysadm-environment#4524

Just in case the logs configuration is faulty.

Refs. swh/infra/sysadm-environment#4524

Refs. swh/infra/sysadm-environment#4524

Refs. swh/infra/sysadm-environment#4524

Refs. swh/infra/sysadm-environment#4524

Refs. swh/infra/sysadm-environment#4524

Refs. swh/infra/sysadm-environment#4524

Refs. swh/infra/sysadm-environment#4524

Refs. swh/infra/sysadm-environment#4524

And bumps the ones identified to need it (lister-maven, lister-all).

With the help of the dashboard [1]

[1] https://grafana.softwareheritage.org/goto/grO2sroVk?orgId=1

Related to swh/infra/sysadm-environment#4707

Future script will serialize this as ' anyways.

the vhost is set by apache to the host it calls (ProxyPreserveHost is
set to false for all the apache configurations)

Related to swh/infra/sysadm-environment#4603

Refs. swh/infra/sysadm-environment#4724

This reverts commit f14e0d8d.

As the charts are becoming more and more complex and critical in the infra,
it could be useful to have some protection against any regressions when
an update is done.

Ref. swh/infra/sysadm-environment#4727

Related to swh/infra/sysadm-environment#4391