Webapp:Cannot add access restriction for scm part of the Webapp if the same adress is already used for the regular site
See original GitHub issue
az feedback
auto-generates most of the information requested below, as of CLI version 2.0.62
Describe the bug If the access restriction has been added for the regular website, and if an extra access restriction is set for the scm-site part is added with the same ip cidr, then an error is thrown back:
cli.azure.cli.core.util : IP address 4.3.2.1/32 already exists.Cannot add duplicate IP address values.
Where 4.3.2.1/32 is the given ip address
To Reproduce az webapp config access-restriction add --resource-group ‘Resource-group’ --name ‘webapp-name’ --action Allow --priority 20 --ip-address ‘4.3.2.1/32’ --rule-name ‘Test1’ --description ‘Test1’
az webapp config access-restriction add --resource-group ‘Resource-group’ --name ‘webapp-name’ --action Allow --priority 20 --ip-address ‘4.3.2.1/32’ --rule-name ‘Test2’ --description ‘Test2’ --scm-site $true
Expected behavior
Adding to the whitelist for the SCM part of the site with the given ip-address
Environment summary Works on azure-cli 2.2.0 Does not work on azure-cli 2.10.1
Additional context Also does not currently work on the azure devops hosted agents and on my machine
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (4 by maintainers)
Top GitHub Comments
@panchagnula I talked to @madsd and he was going to help take a first pass with all the access restrictions related items.
This is fixed by #15784