Use an absolute shebang (/usr/local/bin/python3) because devd runs with a limited environment and does not include /usr/local/bin in its PATH.
This is an exception to the usual #!/usr/bin/env python3 pattern, which cannot work in this context.

• Send all error to STDERR with file=sys.stderr
• Use the OVH /me endpoint to perform a real API call and ensure the credentials are valid and authentication is working

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.

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

!/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)

Removed the extra space

Upgrade to FreeBSD 15 completed successfully.

Fix : 4 spaces beside of one space by convention

command : sudo vtysh

router-002# show ip ospf route
============ OSPF network routing table ============
N    172.27.27.0/27        [10] area: 0.0.0.0
                           directly attached to vmx0

Many changes:

I upgraded Salt to version 3006.23 across all machines.

I also came across OpenOSPFD, an OSPF routing daemon originally developed for OpenBSD, but it is marked as deprecated because it depends on an older CARP implementation.

I’ve noticed that Quagga is now deprecated and has been replaced by FRRouting (FRR), which is actively maintained.