Closed gmuloc closed 1 week ago
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-4121
# Activate the virtual environment
source test-avd-pr-4121/bin/activate
# Install all requirements including PyAVD
pip install "pyavd[ansible] @ git+https://github.com/gmuloc/avd.git@unique-id-regions-and-sites#subdirectory=python-avd" --force
# Install Ansible collection
ansible-galaxy collection install git+https://github.com/gmuloc/avd.git#/ansible_collections/arista/avd/,unique-id-regions-and-sites --force
# Optional: Install AVD examples
cd test-avd-pr-4121
ansible-playbook arista.avd.install_examples
This pull request has conflicts, please resolve those before we can evaluate the pull request.
Conflicts have been resolved. A maintainer will review the pull request shortly.
This pull request has conflicts, please resolve those before we can evaluate the pull request.
Conflicts have been resolved. A maintainer will review the pull request shortly.
Conflicts have been resolved. A maintainer will review the pull request shortly.
Functionality testing successful. I don't see any documentation being updated, and I would have expected to see ->
id: <int; 1-10000; required; unique>
This is captured in the description.
Change Summary
Leverage
unique_keys
introduced in #3725 as plannedComponent(s) name
arista.avd.eos_designs
Proposed changes
CF schema fragment changes
How to test
Tested locally by triggering conflicting scenario (
unique_keys
work as expected)Checklist
Repository Checklist