mozilla-services/circus — pull request #473 by 198d (2013-07-14 20:42:52+00:00)
Title: Empty Includes

Currently, circus will fail to launch when one of the include directives
(include or include_dir) yields an empty set. This seems a little overly
protective and a simple warning emitted into the log should suffice.

Update _scan in read_config to write the previous exception message as a
log message at the warn level.

A little more background:
I'm deploying circus via Salt Stack and have a recipe I share amongst the various roles in our application's infrastructure. One of the config lines I use `include_dir = /etc/circus` and that's worked so far as all of our roles that include circus deploy INI files there and circus hums along. One of our roles needs circus running and is going to be used to dynamically deploy watchers to. I'd like to continue using that base circus module and have circus just ignore the fact that /etc/circus is going to be empty. Also, as stated in the commit message, I simply felt that dying was a little too extreme for a relatively minor issue.