dcnm_vrf: now raises an error if networks are attached during deletion #456
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.
Fix for #455
When networks are attached to a vrf, deletion fails without proper information being raised.
This was because the check for networks was wrong. It was using the VRF switch attachments and not network attachments endpoint.
The check for attached networks is now being done before any updates to the vrf in case a vrf in the config has to be deleted.
Changelog: