-
Notifications
You must be signed in to change notification settings - Fork 119
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
Splits out individual programs to GitHub Riemann org #136
Conversation
I like this, though not 100% sure on splitting out those executables that only require riemann-tools IE: riemann-health, -fd, -diskstats, -net... |
@fborgnia I considered that and then decided that either Riemann-tools was a framework/scaffold or it wasn't - if that makes sense? |
both the repo and gem name suggests to me a set of basic tools, not only scaffolding, besides that i dont see any benefit from splitting those execs that don't require anything else. |
I guess I think it's confusing. Some of the tools are in one gem and a bunch are not. Feels like a mixed signal. If most folks are managing this with configuration management this allows then to be explicit and granular. |
After discussions with @aphyr we're going to wind some of this back - new rule of thumb - broadly tools with dependencies are separate and others are in the riemann-tools gem. |
I've updated the branch to only remove those with dependencies. |
Splits out individual programs to GitHub Riemann org
This series of commits:
Currently none of the extracted programs have been pushed as gems so this is mostly an "on paper" exercise. When they are all pushed as Gems then we'll need to increment the version on this gem, add some warning text and re-push.