Query extensions supported by plugin

[Brad Hall]

We need the ability to query for any extensions that a given plugin supports so that we can make plugin interaction conditional on whether or not it supports the extension. This will be useful in making sure we don't try to do anything that older versions of a plugin doesn't support, etc.

[Brad Hall (bgh)]

The proposed way of doing this is to add another function to the plugin base class called "get_supported_extensions". A plugin will be able to override this method and return a list of extensions that it supports by name.

[Brad Hall (bgh)]

Additionally, we already have supported_extension_aliases as an attribute of the plugin .. maybe we can just expose plugin_supports() from the PluginAwareExtensionManager.

[dan wendlandt (danwent)]

Brad, should this be untargeted from e-4, or are you planning on committing a fix for this in the next few days? Thanks.

[Nataraj Subramanian (nataraj-subramanian)]

Hi, I would like to fix this bug.

I think creating get_supported_aliases() in the plugin base class is a cleaner method. Besides, isn't _plugin_supports() in PluginAwareExtensionManager basically meant to check if the particular extension is supported by a plugin or not? Whereas, here we wish to get the list of all supported extensions by a plugin?

[Nataraj Subramanian (nataraj-subramanian)]

_plugin_supports() could then call get_supported_aliases() and check if the plugin supports it or not.

[dan wendlandt (danwent)]

I think that makes sense. Thanks for taking this on!

[Sumit Naiksatam (snaiksat)]

Just a quick note, doing a GET on the extensions URL already returns a list of the supported extensions for the configured plugin. One can then check if the required extension is in that list or not. We have been using this approach. I believe the proposal here is to provide an API to query whether a particular extension is supported and this will get implemented in the extensions framework?

[dan wendlandt (danwent)]

I agree with Sumit, this is already supported by doing a get on /v1.1/extensions, since the only extensions that are listed are those that the plugin claimed to support.