Skip to content
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

[#puppethack] Adding ability to enable/disable the secruleengine through a parameter #1168

Merged
merged 1 commit into from
Jul 30, 2015
Merged

Conversation

igalic
Copy link
Contributor

@igalic igalic commented Jul 30, 2015

rebase / squash of #1120.

@igalic
Copy link
Contributor Author

igalic commented Jul 30, 2015

still no tests though, cuz, i'm finding them quite pointless in this case.
@bmjen seens to disagree…

@bmjen
Copy link
Contributor

bmjen commented Jul 30, 2015

@igalic I don't think I ever disagreed. :P

I think after looking at the spec tests for mod_security, a unit test is likely not necessary. Will merge once travisci is done.

@jackdpeterson
Copy link

Can this be merged in? I'd like to be the first test-case :-)

igalic added a commit that referenced this pull request Jul 30, 2015
[#puppethack] Adding ability to enable/disable the secruleengine through a parameter
@igalic igalic merged commit ddb76e4 into puppetlabs:master Jul 30, 2015
@igalic
Copy link
Contributor Author

igalic commented Jul 30, 2015

yes, yes it can. (now that travis is done)

@igalic igalic deleted the secrule_engine branch July 30, 2015 17:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants