CI: Fix fabric_name in eos_designs_unit_tests molecule scenario #1755
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
state: CI Updated
ClausHolbechArista
deleted the
fix-eos-designs-unit-tests-fabric-name
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Summary
CI: Fix fabric_name in eos_designs_unit_tests molecule scenario
Related Issue(s)
Currently we have 3 different fabric_name vars in this molecule scenario. This makes the fabric documentation fail or produce changes depending on which host is selected for "run_once".
This will also block the new avd_facts module, where we set facts for all devices in the same fabric_name group
Proposed changes
fabric_nameon this parent group_vars.fabric_namefrom all other group_vars.How to test
Molecule will produce changes to various descriptions and docs where the fabric_name is included.
Checklist
User Checklist
Repository Checklist