This is autogenerated. Please review and update as needed.
Describe the bug
When you specify network ACLs using --network-acls, --network-acls-ips or --network-acls-vnet those parameters are ignored if you also add either the parameter --bypass or --default-action.
As we usually add network ACLs because we want to deny access not specified the current implementation doesn't allow us to do this. Those 3 parameters should always be parsed.
Command Name
az keyvault create
Errors:
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
- Put any pre-requisite steps here...
az keyvault create --name {} --resource-group {} --subscription {} --location {} --enable-soft-delete {} --network-acls-vnets {} --default-action {}
Expected Behavior
Environment Summary
Windows-10-10.0.16299-SP0
Python 3.6.8
Installer: MSI
azure-cli 2.10.0
Extensions:
application-insights 0.1.1
azure-devops 0.17.0
blueprint 0.1.0
Additional Context
This is autogenerated. Please review and update as needed.
Describe the bug
When you specify network ACLs using --network-acls, --network-acls-ips or --network-acls-vnet those parameters are ignored if you also add either the parameter --bypass or --default-action.
As we usually add network ACLs because we want to deny access not specified the current implementation doesn't allow us to do this. Those 3 parameters should always be parsed.
Command Name
az keyvault createErrors:
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
az keyvault create --name {} --resource-group {} --subscription {} --location {} --enable-soft-delete {} --network-acls-vnets {} --default-action {}Expected Behavior
Environment Summary
Additional Context