Skip to content

Remove deprecated cirdrlist parameter from createLoadBalancerRule API #4036

@onitake

Description

@onitake
ISSUE TYPE
  • Improvement Request
  • Documentation Report
COMPONENT NAME
API
CLOUDSTACK VERSION
4.11
and all later versions
CONFIGURATION

N/A

OS / ENVIRONMENT

N/A

SUMMARY

Some networking-related APIs, notably createLoadBalancerRule, support a parameter called cidrlist. This parameter was (presumably) used to automatically manage firewall rules for load balancer rules.

The parameter is deprecated since at least ACS 4.11, leading to an error when trying to use it.

STEPS TO REPRODUCE
create loadbalancerrule publicipid=yyy algorithm=leastconn name=test-lb publicport=9999 privateport=9999 cidrlist=1.2.3.4/32

Specifying openfirewall=true makes no difference.

EXPECTED RESULTS

CloudStack should create a firewall rule for the load balancer.

If this is no longer supported, the parameter should be removed.

ACTUAL RESULTS

cloudmonkey prints the following error:

🙈 Error: (HTTP 431, error code 4350) Parameter cidrList is deprecated; if you need to open firewall rule for the specific CIDR, please refer to createFirewallRule command
OTHER COMMENTS

On a related note, I sent a PR that documents how to send multiple CIDRs in cidrlist: #4035

During preparation of that patch, I identified a few other APIs that use a CIDR_LIST or DEST_CIDR_LIST parameter or return value and may also be affected:

  • CreateEgressFirewallRule
  • CreateFirewallRule
  • CreatePortForwardingRule
  • CreateLoadBalancerRule
  • CreateIpForwardingRule
  • CreateNetworkACL
  • UpdateNetworkACLItem
  • AuthorizeSecurityGroupEgress
  • AuthorizeSecurityGroupIngress
  • CreateVpnCustomerGateway
  • UpdateVpnCustomerGateway
  • FirewallResponse
  • FirewallRuleResponse
  • LoadBalancerResponse
  • NetworkACLItemResponse
  • Site2SiteCustomerGatewayResponse
  • Site2SiteVpnConnectionResponse

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions