-
Notifications
You must be signed in to change notification settings - Fork 36
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
mod_secure_proxy directive causes kitchen converge to fail #48
Comments
@silverl , If I read the error message correctly the Can you try to explain a little bit better what it is you are trying to do and how you are calling the mod_security recipes? Maybe you could share your Frank |
Here's the simplest policyfile-based app I could construct to illustrate the issue (dropbox) I performed the following steps:
kitchen converge errors out as I showed in the logs provided previously. |
To explain what I'm trying to do, I'm trying to create an apache/mod_security web-application firewall starting with the most basic config possible that uses the OWASP CRS. Your cookbook looked like the way to go. I'm relatively new to chef, and trying to adopt the new policyfile workflow. I've programmed for decades, but I don't know much ruby. I assumed I could include your cookbook in my policyfile's runlist, then run my own recipe to configure mod_security using the directives defined in your cookbook. |
@silverl I think I have found the problem, but lost you dropbox files. Can you share them again? |
Very sorry, I can't find the file. I provided complete repro steps earlier. |
I have a very simple Policyfile which does nothing but include mod_security. Running
kitchen converge
works fine, builds up a CentOS box no problem. (Windows host, Vagrant).When I follow your readme.md example and try to add a
mod_secure_proxy
directive, thekitchen converge
fails.The log states:
I don't want to copy your .erb template into my cookbook because that seems non-DRY.
Is there something I'm missing to allow chef to find your template?
Thanks.
The text was updated successfully, but these errors were encountered: