-
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-4816 - new param for mod::security class #1616
MODULES-4816 - new param for mod::security class #1616
Conversation
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.
Can you also add an entry in the readme for this new parameter?
(failures are unrelated to the changes made, but this may need a rebase on the latest commits to pass)
manifests/mod/security.pp
Outdated
| @@ -24,6 +24,7 @@ | |||
| $secrequestbodylimit = '13107200', | |||
| $secrequestbodynofileslimit = '131072', | |||
| $secrequestbodyinmemorylimit = '131072', | |||
| $deploy_security_crs = true, | |||
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.
Could you please name this manage_security_crs to be more similar to other parameters in the module?
- New param $manage_security_crs set to true by default so the default behaviour is unchanged. - new spec example so that the parameter is spec-tested - Add an entry in the doc about this new param
|
Here you are :) I've changed the parameter name and added an entry into the README.md file. |
|
Any news on this one ? |
|
@hunner please review changes |
MODULES-4816 - new param for mod::security class
…urity-param MODULES-4816 - new param for mod::security class
$deploy_security_crsset to true by default so the defaultbehaviour is unchanged.