Set anti affinity policy as separate action with Apstra 4.2.0 #903
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
bwJuniper
approved these changes
Oct 4, 2024
chrismarget-j
deleted the
902-test-testdatasourcedatacenterblueprint-fails-with-420-because-anti-affinity-policy-is-part-of-template
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.
TestDatasourceDatacenterBlueprint()is failing with Apstra 4.2.0 because the test setup code (creating a blueprint) fails to set the Anti Affinity Policy. This is because Apstra 4.2.0 takes the Anti Affinity Policy from the template, rather than the blueprint instantiation request.This PR detects v4.2.0 while prepping Apstra for running the data source, and sets the policy as a separate action when required.
Closes #902