Available in VPC
Delete listeners registered in the load balancer. Even after deletion, there must be at least one listener remaining on the load balancer.
Syntax
The deleteLoadBalancerListeners syntax is as follows:
./ncloud vloadbalancer deleteLoadBalancerListeners \
--loadBalancerListenerNoList <load-balancer-listener-no-list> \
[--regionCode <KR|SGN|JPN>] \
[--output <json|xml>]
Options
This section describes the options available when running deleteLoadBalancerListeners.
Required options
The following options are required for deleteLoadBalancerListeners.
| Options | Type | Required | Description |
|---|---|---|---|
--loadBalancerListenerNoList |
List | Required | List of load balancer listener numbers
|
Common options
For information about the options common to all vloadbalancer subcommands, see Load Balancer (VPC) options.
Examples
If the request to delete a load balancer listener is successful, the configuration information for the listener registered with the load balancer is returned.
Command
The command example is as follows:
./ncloud vloadbalancer deleteLoadBalancerListeners \
--loadBalancerListenerNoList 60002222 \
--regionCode KR \
--output json
Output
The output example is as follows:
{
"deleteLoadBalancerListenersResponse": {
"totalRows": 1,
"loadBalancerListenerList": [
{
"loadBalancerInstanceNo": "41112223",
"loadBalancerListenerNo": "60001111",
"protocolType": {
"code": "HTTP",
"codeName": "HTTP protocol"
},
"port": 80,
"useHttp2": false,
"sslCertificateNo": "",
"tlsMinVersionType": {},
"loadBalancerRuleNoList": [
"70001111"
],
"cipherSuiteList": []
}
],
"requestId": "e1f2a3b4-c5d6-7890-efab-123456789012",
"returnCode": "0",
"returnMessage": "success"
}
}