Tyk Classic API Configuring Plugin Bundles
Last updated: 2 minutes read.
For custom plugins that are deployed as plugin bundles, the API should be configured with the name of the plugin bundle file to download from your remote web server. Furthermore, the Gateway should be configured to enable downloading plugin bundles.
You can configure your API with the name of the plugin bundle file to download within the Tyk Classic API definition or API Designer.
If you’re using the newer Tyk OAS APIs, then check out the Tyk OAS page.
Configuring Plugin Bundles in the Tyk Classic API Definition
The configuration for an API to fetch and download a plugin bundle from a remote server is encapsulated within the custom_middleware_bundle
field of the Tyk Classic API Definition. An illustrative example is listed below:
|
|
With the configuration given in the example above, calls to the API will invoke the custom plugins defined in the manifest.json
file contained within bundle-latest.zip
uploaded to your remote webserver, e.g. http://your-example-plugin-server.com/plugins
.
Tyk Gateway should be configured for downloading plugin bundles from a secured web server. Please consult the plugin bundles documentation for further details.
Configuring plugin bundles in the API Designer
To configure plugin bundles for Tyk Classic APIs click on the APIs menu item in the API Management menu of Dashboard and select your API to display the API editor screen. Subsequently, follow the steps below:
Step 1: Access plugin options
Click on the Advanced Options tab and scroll down until the Plugin Options section is displayed.
Step 2: Enter relative path to bundle file
Enter the relative path of the plugin bundle file in the Plugin Bundle ID field that Tyk Gateway should download from the web server hosting plugin bundles.
Step 3: Save the API
Select the save or update button to apply the changes to your API.