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 :

We can consider the mail server as deployed and create tasks for extra actions in the Mail projects.

Deployed and working fine.

Dovecot deployed and working well.

With Salt, sudo files content are now managed from rOPS.

See also T1784 to improve UX and URLs.

Software has been renamed to Redpanda Connect:

Checked today, it works fine:

Next: configure DNS records

This method works well, Salt automation is welcome.

We can consider we're done and handle the remaining as regular tasks.

All server has been upgraded to FreeBSD 15, excepted router-001, which will be decom when router-002/003 will be live.

https://migration.mediawiki.test.ook.space/w/index.php reports an unknown wiki.

Test URL: https://windriver.nasqueron.org/~dereckson/ops/T1396-nginx-autoindex/

[ Not working actively on this, also we'd need a repro URL. ]

Not working on this for now, and the number of services in our API doesn't make that urgent.

Procedure still the same in current TeX Live Guide, updated the link.

Just a note Flow isn't maintained anymore. The current recommended discussions extension is https://www.mediawiki.org/wiki/Extension:DiscussionTools

At this point, we can consider that the goal "create a wiki farm" is accomplished, and the subtasks are feature requests / bugs to solve in the ongoing cycle.

Will need to be revisited when we switch to acme.sh.

Code responsible to convert the message into a JSON payload, then post it:

@yousra I've noticed I've already created a task with the same issue, with dash character — instead of the non-breaking space here.

Deployed to all servers during meet-up on Jitsi with @ptdradmin and @Duranzed

The tunnel from router-001 to cloudhugger has been destroyed.
172.27.27.253 is now being used to tunnel from router-002 to Ysul

For context, when we apply Salt configuration, it currently checks if ipv6-setup-tunnel is running.

I tried pip install salt==3006.8, but it brings the same strange issue : AttributeError: cannot access submodule 'cmdmod' of module 'salt.modules' (most likely due to a circular import)
(same in WindRiver)

@yousra I think pip install salt==3006.8 should work, with dependencies.

Salt dependencies are reasonable enough to add to requirements.txt:

If Salt dependencies are the issue, a possibility is to define requirements from https://github.com/saltstack/salt/tree/master/requirements