I added a test to determine if the function get_carp_entries() will avoid an FHRP group
if it's not the CARP protocol. Also, it is more readable if we place the CARP configuration directly in the forest.yaml.

testing arc diff

Removed unused imports

Added README.md file for installation steps
Added Nasqueron header in the plugin file

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

Caught this issue during dependencies test.

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

Plugin works, but we need more metadata:

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

Congrats on your first revision. 👍🏻

We need to use OrderedDict from the collections module because the pillar generation script must preserve the order of the information. This ensures that the generated pillar file remains consistent and human-readable. Maintaining a stable order also makes it easier to review changes, compare versions, and debug configurations.

Fixed IDE 2-space formatting across all files, added RouterLink stub to tests, and ensured trailing newlines.

Stripped unrelated logo/navbar/package-lock files and fixed trailing newlines

Reverted accidental OS-specific changes in package-lock.json

I mentioned in D3971 that the requested changes are implemented there.

Fixed 2-space indentation in router and added NotFound unit test

@Chenani-MohamedAmine I appreciate the effort you’ve put into these logo drafts, but I want to reiterate that I had explicitly asked not to move forward with logo work at this stage. Any design work on the branding or logo requires broader discussion with other members of Nasqueron before proceeding.

I've reviewed your changes. I noticed you created a new differential (D3977) instead of updating this one (D3971) for the same task.

Updated hash resolver plugin for terminator :

fix

Here are the final SVG designs for the ServPulse logo.

Hostnames should always be written in lowercase and the node name must match the hostname.

Moving to resolve-hash repository

Moving to resolve-hash repository

Repository move

Not for the operations repository, it's for rRESOLVEHASH.

I came up with this solution which seems to work as intended :

Add the flag ipv6_dhcp_duid for windriver

Fix : when an IPv6 address belongs to the Scaleway tenant, add the
ipv6_dhcp_duid flag in the pillar

Remove an incorrect character from the code (star that shouldn't be there).

I removed the priority and name entries from the generated pillar, as they are not used by Salt in our current setup.
Keeping only the fields actually consumed by the states makes the pillar cleaner and avoids maintaining redundant data.

Use True and False (capitalized) to follow Salt's Python boolean conventions.

Increase the SOA serial so secondary name servers detect the changes and perform a zone transfer.
Ensure DNS records are placed in alphabetical order within the zone file.

Fix priority for CARP in NetBox, and then in the file nodes.sls

Add functions to get the CARP configurations in NetBox

For (1), it was disabled between March 2022 (D2569) and August 2024 (forum thread reporting the issue).