Custom plug-in deployment REST APIs

The information in this page explains how you can deploy custom plug-ins by using the IBM IoT Connected Vehicle Insights Plug-in Deployment Tool, deploy-plugin, on the DevOps server. For information about about deploying custom plug-ins by using the public Plug-in Deployment REST APIs, see Deploying custom plug-ins by using REST APIs.

The IBM IoT Connected Vehicle Insights Plug-in Development Tool is not for general distribution and use outside of IBM. The tool is deployed on the DevOps server for IBM internal use only. If you would like to run the tool to deploy your plug-ins to your IBM IoT Connected Vehicle Insights service instance, then you must obtain a DOU agreement with the IBM IoT Connected Vehicle Insights development team that clearly describes the scope of use and support. If you do not have access to deploy plug-ins from the DevOps server, contact IBM Support to request that your plug-ins are deployed by the IBM Cloud team.

When the service environment is ready to go live, and to be pushed to production, it is classified as being in change-management mode. You cannot deploy plug-ins to a service during change-management mode.

When your plug-ins are successfully deployed and tested, to deploy them to production you must contact IBM Support to raise a formal change request ticket with the IBM Cloud team.

If the IBM IoT Connected Vehicle Insights service is running in a HA environment, during the plug-in deployment process, all of the servers that are in the VDH, Agent System, Context Mapping, or Driver Behavior cluster are stopped and started simultaneously. You cannot choose to stop and start individual servers that are part of a cluster because the deployment process runs synchronously on all servers in the cluster.