Test: Make molecule ansible native

[joelbreton2]

Change Summary

Change molecule testing structure to follow ansible-native configuration
Source

Related Issue(s)

Addresses part of #5990 - the second part (ansible-native)

Proposed changes

• Modify molecule.yml in each test case with 'ansible-native' configuration

How to test

Local: run molecule test --scenario-name <scenario-name>
i.e. molecule test --scenario-name example-single-dc-l3ls

CI: Verify test results

Checklist

User Checklist

• Verify eos_cli_config_gen_deprecated_vars is still required
• Discuss destroy vs cleanup sequence

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-6022
# Activate the virtual environment
source test-avd-pr-6022/bin/activate
# Install all requirements including PyAVD
pip install "pyavd[ansible] @ git+https://github.com/joelbreton2/avd.git@Test--make-molecule-ansible-native#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/joelbreton2/avd.git#/ansible_collections/arista/avd/,Test--make-molecule-ansible-native --force
# Optional: Install AVD examples
cd test-avd-pr-6022
ansible-playbook arista.avd.install_examples

[gmuloc]

so these may be dumb questions, but:

1/ this looks like what I would have expected
2/ don't you need to add more stuff in my crappy empty default/molecule.yml? (maybe not :p )
3/ I am not sure where we rely on default and where not :)
4/ if some test_sequence don't make sense, don't hesitate to adjust them

Would be good to have some rationalization between all our examples :) some of them are (pre-)historical 🦣

[gmuloc]

same maybe lets take the oppotrunity to rename the files the same in every scenario

[joelbreton2]

removed the filename in the path, do you want me to renamed all inventory files to hosts.yml for the inventory.yml remaining?

[gmuloc]

lets align everything for our sanity

[joelbreton2]

All inventory files are now hosts.yml

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[github-actions]

Conflicts have been resolved. A maintainer will review the pull request shortly.

[gmuloc]

as said in one comment let's use the same name for all inventory names

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud