This task required the renewal of the Vault certificate :

Fix : {{ in place of { {

Put the line "# Enable CARP preemption" in the if block so we don't have the
orphan comment in non-router systems.

-Last Update

Update

• Update

Changes :

1. roles/router/carp/files/carp-loader.conf rename on roles/router/carp/files/carp.conf
2. roles/router/carp/files/carp.conf is not a Jinja template
3. The Salt function is now called in the state and its result is passed to the template through the context, it is a convention.

roles/core/network/files/FreeBSD/gre.conf is not a Jinja template.

Normalize to double quotes in Jinja templates as requested

remove .sh

(ah you did it: {{ dirs.bin }}/acmesh-dovecot_postfixReload is well without the extension in D4003)

Oh just I notice here the .sh at line 17, but not at line 16.

remove sudo on each line

I corrected the code.

Add dark mode toggle button : The data-theme attribute, mono theme logic, and Admin Settings are all included in this update.(manually implemented)

Cleaning diff

• Roles: update network pillar

• Modified to create tunnels from router-003

Configured at OVH level.

changed syntax

public address

corrected syntax

Removed hardcoded admin token (thanks to @dereckson)

Test to deploy this final version on Complector with a test=True to see if it's still no-op.

It has been asserted a LDAP is the easiest deployment road for Keycloak operation, supported out of the box, without any custom development needed. If we store users in a MariaDB or PostgreSQL database, we need custom development to explain to Keycloak how to use it.

One of the important thing to note is Keycloak federates user information from external storage.

ALigned ip adresses