-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(MODULES-11061) mod_security custom rule functionality #2145
Conversation
apache::mod::security is a classthat may have no external impact to Forge modules. apache::params is a classBreaking changes to this file WILL impact these 16 modules (exact match):Breaking changes to this file MAY impact these 11 modules (near match):This module is declared in 175 of 576 indexed public
|
Failed checks are not related to the merge. |
@k2patel This change looks good but to go in I'd like it to have some positive test cases, not just the negative ones that you have included. |
@david22swan This should be done, let me know if that works. |
Reducing the string size for matching with wildcard Changing regex based on suggestion from the tests
@david22swan is there any time frame when it would be merged? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Test updates LGTM. :-) |
@k2patel Thanks for putting in the work and getting responding to my comments in such a speedy manner. Thank you again for putting in the effort. |
Basic Info
Module Version: 6.0.0
Puppet Version: 6.21.1
OS Name/Version: RHEL
Apache module activates the mod_security, but there is no way to manage custom rules.
For example, to override rules or create rules, etc.
Desired Behavior:
Allow adding custom rules to the security configuration.
Actual Behavior:
Functionality does not exist.