anchor.diff:       http://127.0.0.1:8080/1.0/kb/tenants/uploadPluginConfig/<pluginName>
   ```
   
  -In a nutshell, the mechanism works in the following way:
  -
  -1. The adminstrator uses the kill bill api to upload the configuration
  +At a high level, the mechanism works in the following way:
  +
  +1. The administrator uses the kill bill API (or Kaui) to upload the configuration
   2. Kill Bill stores the config in the `tenant_kvs` table using a `tenant_key` of `PLUGIN_CONFIG_<pluginName>` and sets the `tenant_value` with the config provided
  -3. Kill Bill broadcasts the change across the cluster of nodes and emit a configuration bus event: `TENANT_CONFIG_CHANGE` or `TENANT_CONFIG_DELETION`
  +3. Kill Bill broadcasts the change across the cluster of nodes and emits a configuration bus event: `TENANT_CONFIG_CHANGE` or `TENANT_CONFIG_DELETION`
   4. The plugin code is *responsible to listen to these events* and take appropriate action to reload/delete its configuration for that specific tenant.
   
   Note that when relying on the plugin frameworks, some amount of work is already provided:
   
  -* For `java` plugins we can see the listener https://github.com/killbill/killbill-plugin-framework-java/blob/killbill-base-plugin-0.3.2/src/main/java/org/killbill/billing/plugin/api/notification/PluginConfigurationEventHandler.java#L37[here],
  -* For `ruby` plugins, the https://github.com/killbill/killbill-plugin-framework-java/blob/killbill-base-plugin-0.3.2/src/main/java/org/killbill/billing/plugin/api/notification/PluginConfigurationEventHandler.java#L33[code exists] for payment plugins created through the https://github.com/killbill/killbill-plugin-framework-ruby#how-to-write-a-payment-plugin-integrated-with-activemerchant[generator].
  -
  +* For `java` plugins we can see the listener https://github.com/killbill/killbill-plugin-framework-java/blob/killbill-base-plugin-1.1.0/src/main/java/org/killbill/billing/plugin/api/notification/PluginConfigurationEventHandler.java#L37[here]
  +* For `ruby` plugins, this is done automatically for https://github.com/killbill/killbill-plugin-framework-ruby/blob/v8.3.1/lib/killbill/helpers/active_merchant/payment_plugin.rb#L48[ActiveMerchant payment plugins]
   
   = Debugging Plugins
   
  
positive.code:      http://127.0.0.1:8080/1.0/kb/tenants/uploadPluginConfig/<pluginName>
  ```
  
  The `<CONFIG>` is treaded as a string and it could be the content of an `xml` or `json` file, a lit of `key-value` parameters,...
  
  ```
  # Retrieve config
  
negative.code: 
  Under `platform`, we will find the following:
  
  * `jruby.jar` : the Runtime JRuby jar that is loaded into killbill for each ruby plugin
  * A set of http://felix.apache.org/downloads.cgi[pure OSGI bundles] (unrelated to Kill Bill plugins) and required for things like OSGI logging, OSGI console, ...
  
  Under `java` and `ruby`, we will find one entry per plugin per version.
  For instance, if we had installed two versions for the ruby `stripe` plugin, we would see the following (`SET_DEFAULT` is a symbolic link that point to the default active version):
  
  ```
  