[
https://issues.apache.org/jira/browse/CLOUDSTACK-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan Purushothama reopened CLOUDSTACK-3170:
----------------------------------------------
I still don't see a button allowing me to edit the parameters of a Network ACL
Item.
> UI: NTier: There is no option/ button made available to update different
> parameters of a Network ACL Item
> ---------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3170
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3170
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
> Affects Versions: 4.2.0
> Reporter: Chandan Purushothama
> Assignee: Brian Federle
> Priority: Blocker
> Fix For: 4.2.0
>
>
> Currently there is only provision to update the rule priority number on the
> UI by moving the rules up and down. There is no provision/button made
> available to update other parameters using the updateNetworkACL API.
> =========================================================================
> As per FS at
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Support+ACL+deny+rules:
> =========================================================================
> updateNetworkACLItem (aliased to updateNetworkACL) - async
> Updates an existing NetworkACLItem
> Parameters:
> id (required) - Id of the network ACL Item
> trafficType (optional) - can be ingress/egress (defaulted to ingress if
> not specified)
> cidrlist (optional) - List of the coma separated CIDRs for the rule. If
> not specified, defaulted to 0.0.0.0/0
> startPort (optional)
> endPort (optional)
> protocol (optional). TCP/UDP/ICMP protocol types are supported
> icmpType (optional) - type of the icmp message being sent
> icmpCode (optional) - error code for this icmp message
> action (optional) - allow/deny
> number (optional) - rule number
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
