Feat(eos_cli_config_gen): Added support for fips_restrictions under management security

[KrasenKolev]

Change Summary

Add support for fips restrictions under management security -> ssl profile. 


Related Issue(s)

Fixes #4760

Component(s) name

arista.avd.eos_cli_config_gen

Proposed changes

add 'fips restrictions' under management security

How to test

Checklist

User Checklist

• N/A

Repository Checklist

• My code has been rebased from devel before I start
• I have read the CONTRIBUTING document.
• My change requires a change to the documentation and documentation have been updated accordingly.
• I have updated molecule CI testing accordingly. (check the box if not applicable)

[github-actions]

Review docs on Read the Docs

To test this pull request:

# Create virtual environment for this testing below the current directory
python -m venv test-avd-pr-4845
# Activate the virtual environment
source test-avd-pr-4845/bin/activate
# Install all requirements including PyAVD
pip install "pyavd[ansible] @ git+https://github.com/KrasenKolev/avd.git@devel#subdirectory=python-avd" --force
# Point Ansible collections path to the Python virtual environment
export ANSIBLE_COLLECTIONS_PATH=$VIRTUAL_ENV/ansible_collections
# Install Ansible collection
ansible-galaxy collection install git+https://github.com/KrasenKolev/avd.git#/ansible_collections/arista/avd/,devel --force
# Optional: Install AVD examples
cd test-avd-pr-4845
ansible-playbook arista.avd.install_examples

[ClausHolbechArista]

You need to pull on your dev machine and then rerun molecule and commit the updates.

[KrasenKolev]

You need to pull on your dev machine and then rerun molecule and commit the updates.

[KrasenKolev]

@ClausHolbechArista, I committed the updates after running the molecule, but by mistake I closed the PR, not sure if something more had to be done.

[Vibhu-gslab]

We need to merge the PR, reopening it

[gmuloc]

@KrasenKolev

you need to rerun the molecule for cv-pathfinder example.
I tried to update the PR but it seems you are not allowing AVD maintainers to push to your branch PR:

To github.com:KrasenKolev/avd.git
 ! [remote rejected]     KrasenKolev/devel -> KrasenKolev/devel (permission denied)
error: failed to push some refs to 'github.com:KrasenKolev/avd.git'

So run locally

cd ansible_collections/arista/avd
molecule converge -s example-cv-pathfinder -- -f 10

[KrasenKolev]

@KrasenKolev

you need to rerun the molecule for cv-pathfinder example. I tried to update the PR but it seems you are not allowing AVD maintainers to push to your branch PR:

To github.com:KrasenKolev/avd.git
 ! [remote rejected]     KrasenKolev/devel -> KrasenKolev/devel (permission denied)
error: failed to push some refs to 'github.com:KrasenKolev/avd.git'

So run locally

cd ansible_collections/arista/avd
molecule converge -s example-cv-pathfinder -- -f 10

@gmuloc that is correct. I was running only:

molecule converge -s eos_cli_config_gen

which is in the contribution guide. I ran it now and committed the changes

[gmuloc]

@KrasenKolev
you need to rerun the molecule for cv-pathfinder example. I tried to update the PR but it seems you are not allowing AVD maintainers to push to your branch PR:

To github.com:KrasenKolev/avd.git
 ! [remote rejected]     KrasenKolev/devel -> KrasenKolev/devel (permission denied)
error: failed to push some refs to 'github.com:KrasenKolev/avd.git'

So run locally

cd ansible_collections/arista/avd
molecule converge -s example-cv-pathfinder -- -f 10

@gmuloc that is correct. I was running only:

molecule converge -s eos_cli_config_gen

which is in the contribution guide. I ran it now and committed the changes

indeed the contribution guide should probably add some info regarding re-running some other molecule scenario when modifying the documentation template that could impact them (though it can be hard to know in advance without running everything which takes quite a while).

@Shivani-gslab can you integrate this to your PR? thanks!