You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The '--endpoint-status' argument value of 'az network traffic-manager endpoint create' is case sensitive and does not behave the way one would expect. If 'Disabled' is specified as the value, the new endpoint has 'Disabled' as the status. If 'disabled' is specified, the new endpoint has 'Enabled' as the status.
To Reproduce
Create a new traffic manager endpoint using 'az network traffic-manager endpoint create' and specify '--endpoint-status disabled' as one of the arguments. Observe that the newly created endpoint is in the 'Enabled' state even though 'disabled' was requested.
Expected behavior
Specifying an invalid value for the endpoint status such as 'invalid' will cause the Azure CLI to print the message that the only valid values are 'Enabled' and 'Disabled'. But the CLI will accept 'disabled' as a value but then treat it as if it was actually 'Enabled'. Either the CLI should reject 'disabled' as invalid or it should accept it and treat it as 'Disabled'.
Environment summary
Azure CLI 2.0.33 on both Windows and Linux
The text was updated successfully, but these errors were encountered:
tjprescott
added
bug
This issue requires a change to an existing behavior in the product in order to be resolved.
Network
az network vnet/lb/nic/dns/etc...
labels
Jun 5, 2018
haroldrandom
added
bug
This issue requires a change to an existing behavior in the product in order to be resolved.
Network
az network vnet/lb/nic/dns/etc...
labels
Oct 25, 2019
Describe the bug
The '--endpoint-status' argument value of 'az network traffic-manager endpoint create' is case sensitive and does not behave the way one would expect. If 'Disabled' is specified as the value, the new endpoint has 'Disabled' as the status. If 'disabled' is specified, the new endpoint has 'Enabled' as the status.
To Reproduce
Create a new traffic manager endpoint using 'az network traffic-manager endpoint create' and specify '--endpoint-status disabled' as one of the arguments. Observe that the newly created endpoint is in the 'Enabled' state even though 'disabled' was requested.
Expected behavior
Specifying an invalid value for the endpoint status such as 'invalid' will cause the Azure CLI to print the message that the only valid values are 'Enabled' and 'Disabled'. But the CLI will accept 'disabled' as a value but then treat it as if it was actually 'Enabled'. Either the CLI should reject 'disabled' as invalid or it should accept it and treat it as 'Disabled'.
Environment summary
Azure CLI 2.0.33 on both Windows and Linux
The text was updated successfully, but these errors were encountered: