-
-
Notifications
You must be signed in to change notification settings - Fork 301
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
Service Provider needs to load_current_resource #15
Comments
May be obvious, but… |
I am not sure It should do this by default. Redis does not contain the ability to simply "reload" so any restart or redis carries with it some serious implications. Perhaps a better idea is to make an attribute that flags it as ok to restart on configuration changes. |
+1 on that :) |
This has been resolved by the fact that I now use the chef service resource instead of a custom redisio_service resource. Done and done! Commit that fixes this is ac4553c |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
The redis_service provider needs to both implement load_current_resource, and also call updated_by_last_action when some action is taken. This will allow it to send notifications and receive subscriptions.
The text was updated successfully, but these errors were encountered: