Allow user to create an ACL Rule for Multiple Ports
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 32
Description
##### ISSUE TYPE
* Improvement Request
##### COMPONENT NAME
~~~
Improvement Request (UI, Functionality)
~~~
##### CLOUDSTACK VERSION
~~~
4.19
~~~
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
##### SUMMARY
Note: This ticket is broken down as requested from the origianl post, https://github.com/apache/cloudstack/issues/8841
**Allow user to create an ACL Rule for Multiple Ports**
- I remember reading somewhere that the logic is supported (Eg. Terraform Provider Docs)
- But the UI doesnt seem to support it.
- This will help greatly reduce the number of rules we create.
##### STEPS TO REPRODUCE
N/A
~~~
N/A
~~~
##### EXPECTED RESULTS
~~~
To be able to manage ACL Rules more easily for large scale projects
~~~
##### ACTUAL RESULTS
~~~
Challenging to use ACL rules for large scale projects.
~~~
Contributor guide
Research direction
The issue names no files or tests. Start by reviewing issue #8841 and the CloudStack UI ACL-rule creation flow, then compare the UI with the Terraform Provider behavior referenced here. Done means the UI can create one ACL rule covering multiple ports and the behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authorization, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100