Reusable ingress/egress rule templates for security groups
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 32
Description
### The required feature described as a wish
Problem: There is currently no way to save or reuse common ingress/egress rule sets across security groups. Every new security group requires rules to be manually re-entered one by one through the UI
Requested behavior: allow users to define and save named rule templates. For instance "baseline-access", "web-server", "database", with options to define specific ports needed. When creating a new security group, allow selection of one or more templates to pre-populate rules
Cloudstack Verison 4.22.0.0
Contributor guide
Research direction
Start by locating the security-group creation entry point and the existing ingress/egress rule model and APIs. Trace how rules are entered and persisted, then identify the tests covering security-group creation; done means named templates can be saved, selected singly or in combination, and used to pre-populate rules with specified ports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- cloud, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100