Use Cases Requiring to Modify the Source Extension JSON Configuration
The Edit Source Extensions panel offers a JSON tab where you can see and modify the whole source extension configuration details (see JSON Tab). You can use this tab to help troubleshoot source extension configuration, but also to change the configuration.
The following table indicates specific indexing pipeline extension use cases that you can only achieve by modifying the source extension JSON configuration.
You can easily apply an extension to a source from the Coveo Cloud V2 administration console (see Applying an Extension to a Source), and then modify its JSON configuration rather than writing it from scratch.
A good practice is to reuse indexing pipeline extensions across two or more sources to prevent creating and having to manage several similar script variants.
You may not be able to reuse an extension because the code needs information that varies from one source to another and that is not available in item metadata. In such a case, the usage of extension parameters could allow you to pass the variable information your code needs to be reusable.
In the JSON tab, you can include one or more parameters and their value such as
In your extension python script, you can get the passed parameter values from the
|Execute a specific extension version||
Each time you modify and save an extension, you create a new extension version. By default, the indeixng pipeline uses the latest extension version.
On some cases, like when you actively develop and extension, you may want to temporarily apply the "stable" version of the extension, not the very last that you saved. You can get the extension version ID value from the Extensions page (see Manage Other Extension Versions).
In the JSON tab, you can specify the
|Action on error||
You can use the optional
The following table describes the available