Algo can be overriden

Algo can be overriden

To put tests in a namespace is certainly a good idea, but that will be in a follow-up commit.

Use os.path.expanduser

Actually, this config CARP will work only in FreeBSD machine because DEVD works only in FreeBSD, so it is not necessary to use dir from map.jinja,
we can put manually the path directory for the scripts that will help the final script carp-ovh-failover that works only in FreeBSD.

Actually, this config CARP will work only in FreeBSD machine because DEVD works only in FreeBSD, so it is not necessary to use dir from map.jinja,
we can put manually the path directory for the scrit carp-ovh-failover and config.yaml.

@dereckson I think it is better to use os.path.expanduser to resolve the user configuration path instead of relying on $HOME, as it provides a more robust and portable way to determine the user’s home directory across environments.

I'm not sure this issue is still relevant as we're reinstalling Ysul in T2315.

Tested here: https://devcentral.nasqueron.org/T2316#36853

Arcanist code has been patched in our production branch @ https://github.com/nasqueron/arcanist

Published as https://github.com/nasqueron/arcanist/commit/2287f8768605272aba2544fa9f4192623f7d05ae

We don't currently track on DevCentral our patches for nasqueron/arcanist, but for reference and documentation of T2316 resolution, it's best to publish it here too.

There are still two things to do:

Deployed to WindRiver.

Added in the commit message the info RID aren't real IP addresses but 32 bits values.

Actually, those scripts should not be placed in the folder bin.

The CARP OVH failover script remains in the folder libexec as it is an internal executable triggered by devd (UNIX conventions).

Removed /var/log/carp.log state because it is created automatically by newsyslog.

We should put the executables in the folder bin, it is the UNIX convention, so in FreeBSD, it will be /usr/local/bin.

-use config dictionary directly instead of intermediate variables
-rename script to .py in repository
-add in config.yaml, the path of the secret

• use /usr/bin/env python3 shebang
• use config dictionary directly instead of intermediate variables
• rename scripts to .py in repository
• refactor init.sls to use a loop for script deployment

Was initially caught by kzonecheck after deployment of the zone file, and before reloading knot.

!/usr/local/bin/python3 uses a fixed Python path, while !/usr/bin/env python3 finds Python dynamically from the system’s PATH,
making it more portable (Python can be installed elsewhere depending on the OS)

Ideal order to merge into main: D4043 then D4044

Removed the extra space

So to clarify for executable scripts files:

March 31 review comments seem to still need action - see https://devcentral.nasqueron.org/D4033#63080