Remove a Block <>vNET associations after vNET IP range change that does not fully match the Block CIDR

Open
#306 1 comment 0 reactions 1 assignee View on GitHub

@DCMattyG is already working on this.

Since Aug 15, 2024.

Assessment

This issue has not been assessed yet.

Description

enhancement

Is your feature request related to a problem? Please describe.
Create a Block and associate a VNETs that falls under the Block CIDR to it.
Change the vNET IP range
Under Configure > Associate , there is an error under Prefix column "ErrNotFound"
Under Discovery > vNETS, IPAM still shows the associations , even though the vNET IP range is updated

Describe the solution you'd like
Automatically, Remove the block <> vNET associations, if all the new IP range of a vnet does not fall under the CIDR of the previously associated Block

Describe alternatives you've considered
Shows a better error messages on both places :
Under Configure > Associate
Under Discovery > vNETS

Dominant language
JavaScript
Stars
327
Forks
111
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/ipam

All issues in Azure/ipam

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.