The script to test if we can access to the OVH credentials (application_key, application_secret, consumer_key):

The script to test the connection to Vault, using a YAML configuration file that tells the secretsmith client how to connect to Vault :

It is not necessary to create a local map.jinja here, since it only imports a variable from the global map.jinja.

1. Install pip using the OS-specific package prefix from map.jinja.

ovh and secretsmith are now installed on the router-002 and router-003.

1.Add map to avoid to hunt version every time we update python.

removed canonical ipv4 from network.sls and corrected node function

better variable name

removed for loop

testing list format for routers

I've asked upstream for advice how to resolve pillar for another server than the current node @ https://groups.google.com/g/salt-tower/c/XEKg2CEiZrU

added router parameter

Light modifications

The output is really useful to avoid to manually repeat the ports.

Rebased. Fixed pillar handling.

In D4026#62889, @dereckson wrote:

Note: we're deploying a third secret for CARP routers scripts. If we've already that code merged, we'll need to append a line to deploy that state too.

updated for loop syntax

Note: we're deploying a third secret for CARP routers scripts. If we've already that code merged, we'll need to append a line to deploy that state too.

Added router-002

Next: try salt web-001 paas_docker.get_upstreams

Removed cloudhugger

Rebased against current main for Alkane.

This change is interesting and should be rebased.

This configuration is for Pixelfed old versions.

Not sure today if we still want to deploy through Docker, or if we would target Alkane PaaS for Espace Win sites. It's also unknown if it brings value to put back the forum archive.

Currently, zed51.dereckson.be serves a 500 error.