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

Reload Nodes on Signal #57

Open
dennis-benzinger-hybris opened this issue Aug 8, 2014 · 1 comment
Open

Reload Nodes on Signal #57

dennis-benzinger-hybris opened this issue Aug 8, 2014 · 1 comment

Comments

@dennis-benzinger-hybris
Copy link

It would be nice if a reload of the nodes could be triggered by a signal. For example SIGHUP.

An example use case is a Rundeck Job which creates new nodes and then runs another job on these new nodes. After creating the nodes the first job would kill -SIGHUP chef-rundeck so that the second job sees the new nodes.

@leftathome
Copy link
Contributor

Frankly I'd rather implement this as something over-the-wire, but if you're in a position to SIGHUP chef-rundeck you should also be able to dump its cached XML response file in its tmp directory. Have you tried that already? Did it give you the results you're looking for?

If not, then what we are looking at is a per-project and/or global cache dump endpoint. Or I guess we could support the PURGE command, Varnish style...

Do we know if Chef search results, partial or otherwise, honor ETags or any other cache-friendly headers?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants