Flex plugins deployment model transition

Effective August 1, 2024, Twilio will transition to a unified deployment model for Flex plugins, discontinuing direct deployments through Twilio Functions and Assets. You will need to use the Flex Plugin Builder (Plugins CLI) for all plugin deployments and modifications. This update simplifies maintenance and upgrades across the platform.

Starting April 1, 2025, any legacy plugins that have not been migrated to the new system will stop working within the Flex UI. It’s crucial that you migrate your plugins before this date to avoid any disruption in service. 
Updated 25-Sept-2024: Previously, this changelog entry stated that non-migrated legacy plugins would stop working on November 20, 2024. The deadline has been extended to April 1, 2025.

Previously, Flex plugins could be directly deployed and modified via Twilio Console or the Serverless Toolkit, allowing flexibility in management but varying in standardization.

These changes are aimed at enhancing security and manageability without impacting system performance. We encourage you to follow these steps to ensure a seamless transition:

• Identify your legacy plugins: Review your Flex custom plugins to determine which of your deployments are considered legacy plugins. 
• Install the Flex Plugin CLI: If you haven’t already, use the Twilio CLI documentation to install the Twilio CLI on your local machine. Then, install the Flex Plugins CLI to ensure you have the necessary tools for migration. 
• Follow the migration guide: Our Flex plugins migration guide outlines all necessary steps to reinstall your plugins without impacting your ongoing operations.