customization: plugins and extensions about invenio-app-rdm HOT 3 CLOSED

What is the difference we make between a plugin and an extension?

from invenio-app-rdm.

Plugin: There is a specific API to be implemented, then it is "plugged-in" into an existing invenio-module (e.g. previewers, authentication, storage back-ends). Support for backward compatibility.

Extension: i.e. Flask extensions. For example GitHub, you can authenticate with it, but you can also do everything GitHub allows you to (e.g. via webhooks). For example list, add, etc. repositories. Therefore, it is a significant amount of code, without a defined API. No support for backward compatibility.

from invenio-app-rdm.

These 2 things are the same for our purposes: just extension.

Each extension needs to document how/what needs to be loaded in the entrypoint and how the configuration needs to be set in the invenio.cfg (and sometimes that means importing and overriding in the invenio.cfg)

from invenio-app-rdm.