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

Changes to certificate files do not trigger notifications #1

Closed
gadgetmg opened this issue Sep 11, 2014 · 3 comments
Closed

Changes to certificate files do not trigger notifications #1

gadgetmg opened this issue Sep 11, 2014 · 3 comments

Comments

@gadgetmg
Copy link

Whenever I make a change to the certificate or private key, the files are updated as expected, but notifications in the ssl_certificate resource are not triggered. For example, if I change the certificate for an nginx instance, I want to notify nginx to restart.

@zuazo
Copy link
Owner

zuazo commented Sep 11, 2014

Hi @gadgetmg, thanks for the report.

Can you specify what kind of changes are you talking about? I want to try to reproduce it to see where the bug is. In theory, the notification should be triggered whenever the certificate file is updated (in theory).

@gadgetmg
Copy link
Author

In my test, I'm just specifying the certificate and key in node attributes. If I update the certificate in the attribute, like for renewal for example, it does update the files on the node, but it doesn't send the notification to the resource I've specified with the notifies command, in this case restarting the nginx service.

@zuazo zuazo closed this as completed in ba5c1a0 Sep 13, 2014
@zuazo
Copy link
Owner

zuazo commented Sep 14, 2014

Hello @gadgetmg, I just released the version 0.2.1 with a fix for this problem. Thanks again for reporting.

zuazo pushed a commit that referenced this issue Nov 27, 2016
Added documentation for key_length and extended_key_usage parameters.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants