Work with VNETs with multiple address spaces

[51lver]

Hello guys,

First of all, thank you for this solution!
One thing to add - the current solution, I guess, doesn't work with VNET's containing a few address spaces.

Will be very nice to add it.

[gamullen]

Thanks. Are you able to make any code changes?

[51lver]

I have no experience with C# 🤷

[gamullen]

@51lver - I added the functionality to the code.

[51lver]

Update - resolved
Hello Gary! @gamullen
Sorry for long delay, I tried to deploy the function using the Azure function core tools...
Is there anything I'm doing wrong? I know it's not related to this specific GH issue

[gamullen]

@51lver Looks as though you figured it out?

[51lver]

yes

[51lver]

@gamullen OK i tested the function, it works. Thanks!
I tried to test if it works with multiple address spaces, but I'm still not sure...
So for example, if I have 2 spaces (/26 + /27) and /26 has only space for /28 subnet, and I'm looking for /27 cidr, will it be found in the /27 space?

[gamullen]

If you have an address space in your VNet that is 10.0.0.0/26, and you want to get a 28 subnet out of it, you'd pass in "&cidr=28&addressSpace=10.0.0.0/26"

[51lver]

So by default (without address space in the request) it won't use all the spaces for searching?

[gamullen]

No - the first space that is returned by the API is used if the subnet fits. If you want to target a specific address space specify it.

[51lver]

@gamullen If you don't mind I'll try to add the work with a few spaces as a default option.

[gamullen]

Not sure what you mean. The code should go through all address spaces until it finds a suitable subnet. I just don't control the order in which the address spaces are processed.