-
-
Notifications
You must be signed in to change notification settings - Fork 883
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
ssl_cert => 'puppet:///modules/sslkey/wildcard_mydomain.crt' doesn't work after upgrade #638
Comments
It seems like that it was introduced in commit be4decd. |
@yarikdot I'm sorry about that. This is one of the reasons we have removed any kind of SSL cert/key management from the module (because we don't know how everyone's doing it to start with). The module now requires any certificates, keys, and other SSL files to be copied in whatever manner the admin sees fit, and you then must specify the path to that file in the module. In your case you will need a bit of boilerplate code that sits outside the module to copy the file from the server to the client. There's a bit more about my rationale here: #599 |
Nothing to be sorry about. Evolution sometimes brings some victims. Would you mind updating the README file, section "Example puppet class calling nginx::vhost with HTTPS FastCGI and redirection of HTTP". The puppet:// is still there and it might be confusing for somebody. |
This one got me, too. Fair enough as a change, but should surely have been marked as a breaking change? |
We did upgrade to the latest version of your great plugin and unfortunately this construction stopped working:
When applied the changes after module upgrade we see and of course nginx crashed:
The text was updated successfully, but these errors were encountered: