Custom connectors
Custom connectors are identified based on their presence and version compatibility with the connector repository. A connector is deemed custom if it:- Is not listed in Connector Configuration Reference.
- Has a version that differs from what is available in the repository.
Furthermore, only connectors following the version 2 (v2) architecture, also known as non-classic connectors, are recognized as custom.
Connector repository
Connectors such as “kaltura (v2)” and “solr (classic)” are available in the repository with specific versions and SDK compatibility. You can see this information at the/api/connectors/repository
endpoint.
Deployed connectors
Examples includelucidworks.workday
, lucidworks.kaltura
, and lucid.solr
marked as DEPLOYED
in Fusion’s connectors list.
You can see this information at the /api/connectors/plugins
endpoint.
Custom connector criteria
lucidworks.kaltura
is custom due to its unique developmental version0.1.0-dev.565.uncommitted+kaltura.5.4.nwm.1217913
not matching the repository’s version0.0.1
.lucidworks.workday
qualifies as custom because it is absent in the repository.lucid.solr
is not considered custom as it is a classic connector.- https://fusion-host/api/connectors/plugins/lucidworks.kaltura
Storage of custom connectors
Custom connectors are systematically stored in the_lw_system/connectors-plugins
folder within the config-sync repository.