Volumes and environments are updated per getsentry/self-hosted repository.
Previously, services was defined separately for sentry web/cron/worker,
but the three was run form roles/paas-docker/containers/sentry.
Services are configured like for Snuba in D2881, each container uses
the same image, with a different launch command, especially as there
are now new ones.
Realm settings are refactored and contain service hosts information,
as we don't use links anymore. A realm will have a set of configuration
files.
The Sentry configuration is written in Python. This change provides
a configuration based on the getsentry/self-hosted one with:
- services configured through the realm pillar
- credentials directly fetched from Vault by Sentry itself
A Vault policy is provisioned for Sentry configuration.
Ref T1791