Improve query which discovers device profile to handle dp clones #631
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
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.
Under some circumstances (outlined in #625), Apstra may double-import a device profile from the Global Catalog (aos_library). The behavior is documented in AOS-45682 and corrected in PR 29925.
Those situations break the
apstra_datacenter_device_allocationresource's assumption that a given Device Profile will appear only once in the graph DB.This PR improves the query used for discovering the correct Device Profile node so that we find the correct node even when multiple DP with identical
device_profile_idattributes appear in the graph db.No tests exist for this behavior - testing this situation requires agents - something we can't currently emulate with our automated test setup.
Closes #625