Support Destination CIDR
- 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
**Support Destination CIDR**
- Reduces number of ACL Rules required
- Adds more security
- Makes ACL rule function more complete
##### 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
Start by reading the linked original issue #8841 and the existing ACL-rule documentation or entry points; this issue names no files or tests. Before implementation, clarify the expected destination-CIDR behavior and acceptance criteria, then identify the affected components and tests. Done means destination CIDR can be managed for ACL rules with coverage for the agreed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100