Fix a typo on the title

LTGM for what it's worth ;)

The site is deployed and available at https://azure-billing.internal.admin.swh.network/

add the tfstate update after the creation of the server

Thanks olasd for restarting the service following this documentation: https://docs.gunicorn.org/en/stable/signals.html#upgrading-to-a-new-binary-on-the-fly

First, replace the old binary with a new one, then send a USR2 signal to the current master process. It executes a new binary whose PID file is postfixed with .2 (e.g. /var/run/gunicorn.pid.2), which in turn starts a new master process and new worker processes:
At this point, two instances of Gunicorn are running, handling the incoming requests together. To phase the old instance out, you have to send a WINCH signal to the old master process, and its worker processes will start to gracefully shut down.

Sorry the description was not completely clear
The durations metrics are still updated, but not the operations count ones
In 2 metrics at 10 minutes of interval:

vsellier@saam ~ % ls -al /tmp/m[12]              
-rw-r--r-- 1 vsellier vsellier 176850 Mar 30 07:25 /tmp/m1
-rw-r--r-- 1 vsellier vsellier 176846 Mar 30 07:34 /tmp/m2

the scripts finally land in the puppet repository (D7456)

Remove useless debug logs leaking the azure credentials

The test instance can be reached at https://gitlab-staging.swh.network

The diff is now ready to be reviewed.
We will start with a manual deployment in a first time

split gitlab installation from the aks configuration

same

fix output typos

a couple of non-blocking remarks in lined

other more general points, not directly relative to this diff:

• the image should be build from adoptopenjdk/openjdk11:debian-jre or any debian based image
• The user used in the container seems to be root, doesn't it generate some permissions issues in the temporary directory?

• Review feedbacks
• Add a report generation in html + an index page
• Add a nginx container to export the html files
• Use a docker volume to avoid permission issues in the output directory
• Ensure the csv is downloaded each time a docker-compose up is launched
• use the requirements.txt file to install the dependencies in the image

The following installation methods were tested:

1. debian packages
2. docker image
3. helm charts
4. gitlab operator

A working poc is implemented in the snippet repository for now.

btw: This is some examples of the output of the script: P1312

Remove useless commented code

@zack Do you know when the internship will end? (to schedule a reminder for the account removal)

The replication is in place:

root@backup01:~# zfs list -t all
NAME                                                                 USED  AVAIL     REFER  MOUNTPOINT
data                                                                 120G  72.5G       96K  none
data/sync                                                            120G  72.5G       96K  none
data/sync/dali                                                       120G  72.5G       96K  none
data/sync/dali/postgresql                                            120G  72.5G     73.2G  none
data/sync/dali/postgresql@autosnap_2022-02-08_19:04:44_monthly      22.9G      -     72.3G  -
data/sync/dali/postgresql@autosnap_2022-02-18_00:00:01_daily        3.11G      -     73.2G  -
data/sync/dali/postgresql@autosnap_2022-02-19_00:00:01_daily        2.43G      -     73.2G  -
data/sync/dali/postgresql@autosnap_2022-02-20_00:00:01_daily        2.39G      -     73.2G  -
data/sync/dali/postgresql@autosnap_2022-02-21_00:00:01_daily        2.44G      -     73.2G  -
data/sync/dali/postgresql@autosnap_2022-02-22_00:00:00_daily        2.47G      -     73.2G  -
data/sync/dali/postgresql@autosnap_2022-02-23_00:00:02_daily        2.56G      -     73.2G  -
data/sync/dali/postgresql@autosnap_2022-02-24_00:00:00_daily           0B      -     73.2G  -
data/sync/dali/postgresql/wal                                        600M  72.5G     88.4M  none
data/sync/dali/postgresql/wal@autosnap_2022-02-08_19:04:44_monthly  61.9M      -     61.9M  -
data/sync/dali/postgresql/wal@autosnap_2022-02-18_00:00:01_daily    90.9M      -      107M  -
data/sync/dali/postgresql/wal@autosnap_2022-02-19_00:00:01_daily    94.7M      -      111M  -
data/sync/dali/postgresql/wal@autosnap_2022-02-20_00:00:01_daily    55.4M      -     87.5M  -
data/sync/dali/postgresql/wal@autosnap_2022-02-21_00:00:01_daily    50.1M      -     98.2M  -
data/sync/dali/postgresql/wal@autosnap_2022-02-22_00:00:00_daily    57.7M      -      106M  -
data/sync/dali/postgresql/wal@autosnap_2022-02-23_00:00:02_daily    52.8M      -     68.8M  -
data/sync/dali/postgresql/wal@autosnap_2022-02-24_00:00:00_daily       0B      -     88.4M  -

The retention will 2 monthly snapshots and 30 daily snapshots
The space occupation should be just around 200Go so we will probably have to extend a little the data disk.