After some consideration and thought we are going to move all plugin extensions to sensu/sensu-extensions. I know I said everything related to an app would be self-contained but the problem lies in how an extension functions.
http://sensuapp.org/docs/0.16/extensions
Generally speaking if you introduce a bug into a plugin it will only affect that plugin. We do/will be writing tests for this to protect the stability of the plugins. Extensions by their nature run outside of the plugin and have the ability to adversely affect the Sensu server itself. Tests can be written to account for this but they are generally more indepth and require a fair about of knowledge of how sensu works.
At this time I am going to pull extensions from the repo’s contained in the sensu-plugins org for possible inclusion in the above repo. This will help to ensure that anyone using the extensions will at least be aware that they are far more powerful than normal checks or even mutators, which just affect the data.
This in no way will affect the sensu-community-plugins repo. Any new extensions going forward should be pulled against the above repo though and it should be considered authoritative.
···
Matt Jones @DevopsMatt
Infrastructure Engineer - Yieldbot Inc.
Core Contributor - Sensu Plugins
We will be creating a new repository for community extensions, as the “sensu-extensions” repository is for built-in extensions.
Sean.
···
On Apr 29, 2015 11:42 AM, “Matt Jones” mattjones@yieldbot.com wrote:
After some consideration and thought we are going to move all plugin extensions to sensu/sensu-extensions. I know I said everything related to an app would be self-contained but the problem lies in how an extension functions.
http://sensuapp.org/docs/0.16/extensions
Generally speaking if you introduce a bug into a plugin it will only affect that plugin. We do/will be writing tests for this to protect the stability of the plugins. Extensions by their nature run outside of the plugin and have the ability to adversely affect the Sensu server itself. Tests can be written to account for this but they are generally more indepth and require a fair about of knowledge of how sensu works.
At this time I am going to pull extensions from the repo’s contained in the sensu-plugins org for possible inclusion in the above repo. This will help to ensure that anyone using the extensions will at least be aware that they are far more powerful than normal checks or even mutators, which just affect the data.
This in no way will affect the sensu-community-plugins repo. Any new extensions going forward should be pulled against the above repo though and it should be considered authoritative.
–
Matt Jones @DevopsMatt
Infrastructure Engineer - Yieldbot Inc.
Core Contributor - Sensu Plugins