Rename sensor_info: services to sensor / drush to sensor-config

Shouldn't be easy to rename the plugin id and drush command to sensor-config? We could also go with just monitoring-sensor, but given that we have sensor-result as well...

Renamed quite some stuff. from sensor-info to sensor-config

+++ b/monitoring.drush.inc
@@ -41,15 +41,15 @@ define('MONITORING_DRUSH_SENSOR_STATUS_OK', 0);
-  $items['monitoring-info'] = array(
+  $items['monitoring-config'] = array(
     'callback' => 'monitoring_drush_info',

Question here is if this makes sense I guess, or if it should be monitoring-sensor-config, but we just have monitoring-something for all commands and they are all sensor related.

There is no "sensor" to drop in the drush commands? I was wondering about the opposite, *adding* it. But I think that's a different discussion and we would have to rename everything then.

RTBC then I think. Note that this will change the public URL's, so we should make sure that's what we want and are going to keep it...

As commented in #2384601: Rename Sensor to SensorPlugin, we should extract everything drush/services related from that patch that's not already here and do that separately.

changed dush.inc as pointed out in #2384601: Rename Sensor to SensorPlugin.

1. +++ b/modules/demo/monitoring_demo.install
   @@ -19,7 +19,7 @@ function monitoring_demo_install() {
   -    'monitoring-sensor-info' => array(
   +    'monitoring-sensor-config' => array(
   

   We decided to rename the rest plugin to just monitoring-sensor. Also remove the Config from the resource class name then.

   There are also some arguments in there, like expand on 'sensor_info', change that to 'sensor' as well.

   drush.inc and and both Resource classes should no longer contain any "sensor_info" or "sensor-info", probably also no "info" at all.

2. +++ b/monitoring.drush.inc
   @@ -41,15 +41,15 @@ define('MONITORING_DRUSH_SENSOR_STATUS_OK', 0);
   -  $items['monitoring-info'] = array(
   +  $items['monitoring-sensor-config'] = array(
   ...
   -      'drush monitoring-info' => 'Prints sensor config for all available sensors.',
   -      'drush monitoring-info node_new' => 'Prints info of the node_new sensor.',
   +      'drush monitoring-config' => 'Prints sensor config for all available sensors.',
   +      'drush monitoring-config node_new' => 'Prints info of the node_new sensor.',
   

   Examples need to be updated.

Okay reworked, no more info or config.

Yep, #2183983: Find hidden configuration schema issues happened, so all tests by default enforce a valid config schema.

Can be temporarily disabled by setting that flag in our base test classes to FALSE, I suggest we do that, and then work on the config schema issue, which now allows to easily validate that our config schema is correct.