Skip to content

Add protocol parameter to "application-gateway http-listener" and "application-gateway listener" Commands #29208

@gdhillon24

Description

@gdhillon24

Describe the bug

Add protocol parameter to "application-gateway http-listener" and "application-gateway listener" Commands
Currently "az network application-gateway http-listener create" and "az network application-gateway listener create" do not have protocol parameter and if --ssl-cert parameter is mentioned it implicitly creates a HTTPS or TLS listener. And this is confusing for the customers.

Example cmdlet having protocol parameter : az network application-gateway http-settings create

**Important Notes:

  1. Please make sure it does become a breaking change and should not impact existing customers. It should be an optional parameter.
  2. Could you please update the Documentation description for these commands, if the protocol and ssl cert parameter is not set then by default it creates Http Listener and if ssl cert parameter is set it creates Https Listener. Similarly for application-gateway listener commands. Please contact me in case you need additional information**

Related command

az network application-gateway http-listener create
az network application-gateway listener create
az network application-gateway http-listener update
az network application-gateway listener update

Errors

commands do not support protocol parameter

Issue script & Debug output

commands do not support protocol parameter

Expected behavior

commands should have protocol parameter

Environment Summary

azure-cli 2.39.0 *

core 2.39.0 *
telemetry 1.0.6 *

Extensions:
azure-devops 0.23.0

Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.1.0b1

Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\gdhillon.azure\cliextensions'

Python (Windows) 3.10.5 (tags/v3.10.5:f377153, Jun 6 2022, 15:58:59) [MSC v.1929 32 bit (Intel)]

Legal docs and information: aka.ms/AzureCliLegal

Additional context

Please make sure it does become a breaking change and should not impact existing customers.

Metadata

Metadata

Assignees

Labels

Auto-AssignAuto assign by botAuto-ResolveAuto resolve by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamNetworkaz network vnet/lb/nic/dns/etc...questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions