{APIM} public network access parameter values should be Enabled or Disabled

[navba-MSFT]

fixes https://github.com/Azure/azure-rest-api-specs/issues/23683

This REST API where it clearly talks about the --public-network-access accepting the values Enabled or Disabled.

Seeing the REST API Specs swagger, I see the accepted values are Enabled or Disabled.

However in Azure CLI, apim update and apim create is expecting true or false. This is causing an unexpected behavior with the apim creation and updating the --public-network-access setting.

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change [Component Name 2] az command b: Add some customer-facing feature

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• [x] The PR title and description has followed the guideline in Submitting Pull Requests.

• [x] I adhere to the Command Guidelines.

• [x] I adhere to the Error Handling Guidelines.

[azure-client-tools-bot-prd[bot]]

️✔️AzureCLI-FullTest

️✔️acr

️✔️2020-09-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️acs

️✔️2020-09-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️advisor

️✔️latest

️✔️3.10

️✔️3.9

️✔️ams

️✔️latest

️✔️3.10

️✔️3.9

️✔️apim

️✔️latest

️✔️3.10

️✔️3.9

️✔️appconfig

️✔️latest

️✔️3.10

️✔️3.9

️✔️appservice

️✔️latest

️✔️3.10

️✔️3.9

️✔️aro

️✔️latest

️✔️3.10

️✔️3.9

️✔️backup

️✔️latest

️✔️3.10

️✔️3.9

️✔️batch

️✔️latest

️✔️3.10

️✔️3.9

️✔️batchai

️✔️latest

️✔️3.10

️✔️3.9

️✔️billing

️✔️latest

️✔️3.10

️✔️3.9

️✔️botservice

️✔️latest

️✔️3.10

️✔️3.9

️✔️cdn

️✔️latest

️✔️3.10

️✔️3.9

️✔️cloud

️✔️latest

️✔️3.10

️✔️3.9

️✔️cognitiveservices

️✔️latest

️✔️3.10

️✔️3.9

️✔️config

️✔️latest

️✔️3.10

️✔️3.9

️✔️configure

️✔️latest

️✔️3.10

️✔️3.9

️✔️consumption

️✔️latest

️✔️3.10

️✔️3.9

️✔️container

️✔️latest

️✔️3.10

️✔️3.9

️✔️core

️✔️2018-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2019-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2020-09-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️cosmosdb

️✔️latest

️✔️3.10

️✔️3.9

️✔️databoxedge

️✔️2019-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2020-09-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️dla

️✔️latest

️✔️3.10

️✔️3.9

️✔️dls

️✔️latest

️✔️3.10

️✔️3.9

️✔️dms

️✔️latest

️✔️3.10

️✔️3.9

️✔️eventgrid

️✔️latest

️✔️3.10

️✔️3.9

️✔️eventhubs

️✔️latest

️✔️3.10

️✔️3.9

️✔️feedback

️✔️latest

️✔️3.10

️✔️3.9

️✔️find

️✔️latest

️✔️3.10

️✔️3.9

️✔️hdinsight

️✔️latest

️✔️3.10

️✔️3.9

️✔️identity

️✔️latest

️✔️3.10

️✔️3.9

️✔️iot

️✔️2019-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2020-09-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️keyvault

️✔️2018-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2020-09-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️kusto

️✔️latest

️✔️3.10

️✔️3.9

️✔️lab

️✔️latest

️✔️3.10

️✔️3.9

️✔️managedservices

️✔️latest

️✔️3.10

️✔️3.9

️✔️maps

️✔️latest

️✔️3.10

️✔️3.9

️✔️marketplaceordering

️✔️latest

️✔️3.10

️✔️3.9

️✔️monitor

️✔️latest

️✔️3.10

️✔️3.9

️✔️netappfiles

️✔️latest

️✔️3.10

️✔️3.9

️✔️network

️✔️2018-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️policyinsights

️✔️latest

️✔️3.10

️✔️3.9

️✔️privatedns

️✔️latest

️✔️3.10

️✔️3.9

️✔️profile

️✔️latest

️✔️3.10

️✔️3.9

️✔️rdbms

️✔️latest

️✔️3.10

️✔️3.9

️✔️redis

️✔️latest

️✔️3.10

️✔️3.9

️✔️relay

️✔️latest

️✔️3.10

️✔️3.9

️✔️resource

️✔️2018-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2019-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️role

️✔️latest

️✔️3.10

️✔️3.9

️✔️search

️✔️latest

️✔️3.10

️✔️3.9

️✔️security

️✔️latest

️✔️3.10

️✔️3.9

️✔️servicebus

️✔️latest

️✔️3.10

️✔️3.9

️✔️serviceconnector

️✔️latest

️✔️3.10

️✔️3.9

️✔️servicefabric

️✔️latest

️✔️3.10

️✔️3.9

️✔️signalr

️✔️latest

️✔️3.10

️✔️3.9

️✔️sql

️✔️latest

️✔️3.10

️✔️3.9

️✔️sqlvm

️✔️latest

️✔️3.10

️✔️3.9

️✔️storage

️✔️2018-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2019-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2020-09-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️synapse

️✔️latest

️✔️3.10

️✔️3.9

️✔️telemetry

️✔️2018-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2019-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2020-09-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️util

️✔️latest

️✔️3.10

️✔️3.9

️✔️vm

️✔️2018-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2019-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2020-09-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

[azure-client-tools-bot-prd[bot]]

Hi @navba-MSFT, Since the current milestone time is less than 7 days, this pr will be reviewed in the next milestone.

[yonzhan]

APIM

[zhoxing-ms]

Could you please add a test for this case?

[zhoxing-ms]

@navba-MSFT Any update?

[navba-MSFT]

@navba-MSFT Any update?

I will check this and get back to you.

[zhoxing-ms]

@navba-MSFT Please note that we are launching the release for this sprint this week. Please resolve all comments by tomorrow, otherwise the release of this PR will have to be postponed to the next sprint (on 08-01)

[zhoxing-ms]

@Anand0046 Could you please help review the APIM related PR?

[yanzhudd]

@navba-MSFT please note that there is a code freeze for this sprint in 9-19. Please resolve all comments before the date, otherwise this PR will have to be postponed to next sprint (11-07).