Each test run produces this:

Actually, we use the same database name than for MariaDB / MySQl:

Bruteforce attack scenario possible, so we're only interested by usernames defined in users.sls, not by "root" (can't login by SSH) or generic accounts like "docker" (doesn't exist):

Checking the RabbitMQ Monitoring with Prometheus guide:

• we're OK for cluster name
• to get sensible values for rate() in Grafana, we need to configure Prometheus to scrape RabbitMQ every 15s ; according Prometheus configuration, the value scrape_interval can be set at job level

Grafana dashboard was full N/A.

Here we are with D3812 build:

That builds properly:

In T1098#21963, @dereckson wrote:

Tested a build manually successfully with:

$ git clone https://github.com/Learath2/sBNC.git
$ cd sBNC
$ cc *.c -o sbnc
$ sudo cp sbnc /usr/local/bin

Mail solution currently use Dovecot.

Same issue for rhyne-wyse.log. Configuration was copied from acme.sh one.

It's somewhat still maintained:

tikv is marketed as a distributed, solid, high-performant key/value store.

sys-info support for FreeBSD has been added if it was previously a blocker.

May 2020 - https://github.com/FillZpp/sys-info-rs/blob/master/c/freebsd.c

Package has been added in January 2022.

Two blockers at app-level:

• .env support is missing from application code.
• code need to be upgraded to test MySQL connectivity

Credentials
Password created in ops/secrets/dbserver/cluster-B/users/obsidian51

Credentials have been hashed directly in Vault, so we don't need to manipulate cleartext password with Salt.
Salt updated the tomcat-users.xml accordingly.

web-001 upgrade ready, next step: reboot and run again freebsd-update install

We switched to a dynamic approach for init.sls in D3334.

The full /etc/nginx directories on both docker-002 and dwellers use httpd_config_t for every file.

With T1452 resolved, this is resolved too.