The twilio flex:plugins:deploy
command automates the process of uploading your plugin to Flex. This allows you to deploy your plugins via the command line, without needing to manually upload them using a GUI. After a deploy, your plugin is not yet enabled for all your users on your Flex application. You need to run the release
command after the deploy to enable any changes.
The twilio flex:plugins:release
command is used to change which plugins are live for your users. You can group multiple plugins into a release, and you can re-activate any prior release to rollback changes.
This guide includes examples for deploying and releasing your Flex plugins.
You need to install the latest version of the Flex Plugins CLI in order to use these features. If you're migrating a legacy plugin to use the new CLI, refer to our Migration Guide.
_10twilio flex:plugins:deploy --major --changelog "Notes for this version" --description "Functionality of the plugin"
The deploy
command does the following:
--public
to your
deploy
command.
--major
flag is passed. This creates a new major version of the plugin (ex: v1 to v2), and it stores the provided changelog along with your new version. If a version option (
major
,
minor
, or
patch
) is not provided, the
deploy
command defaults to a new patch version.
package.json
of your plugin to the new version.
description
option does not need to be provided on additional deploys.
Releasing plugins is a two-step process using the Plugins API.
The Plugins CLI release
command combines both of these steps to simplify the most common scenarios.
You can create a release by listing each of the plugins that should be active for your users:
_10twilio flex:plugins:release --plugin example-plugin@1.0.0 --plugin additional-plugin@2.1.0 --name "Example 1" --description "Demonstrating use of twilio flex:plugins:release"
The release
command does the following:
When constructing a new release:
--plugin
argument takes the plugin you want to enable in the format
plugin-name@version.
Multiple plugins can be grouped into a release by using
--plugin
for each plugin that should be enabled.
--name
and
--description
options. These can be used to describe what changed within this release, and these details will be displayed within the Plugins Dashboard. These are a useful reference when reviewing your release history or choosing to re-deploy a prior release.
A new configuration does not need to be immediately released to users. You can instead create a configuration first and then pass in a reference to the configuration when creating a release. This is similar to the process you'll use to re-deploy a prior release.
First, create a new Flex Plugin Configuration:
_10twilio flex:plugins:create-configuration --name "Example config1" --description "Testing new plugins" --plugin plugin-test-example@1.0.0 --plugin <additional-plugin-name>@<version>
This command will create a new configuration and return the SID of your new resource. You can lookup the SID of a configuration by running:
_10twilio flex:plugins:list:configurations
Finally, create a new Release with your provided Flex Plugin Configuration:
_10twilio flex:plugins:release --configuration-sid <Configuration Sid>
By default, the release
and create-configuration
commands will merge the list of plugins you provide with the plugins that are on the active configuration. This behavior can be changed with the --new
argument. Suppose you have two plugins live: plugin-alpha@1.0.1
and plugin-beta@2.1.1
. A new v1.1.0 version of plugin-alpha
has been deployed, and you are creating a new release:
Without --new (default)
_10twilio flex:plugins:release --plugin plugin-alpha@1.1.0 --name "Bumping Alpha" --description "Alpha and Beta both up-to-date"
In this release, plugin-alpha
is updated to the version provided in the command. plugin-beta
stays enabled on the active version.
With --new
_10twilio flex:plugins:release --new --plugin plugin-alpha@1.1.0 --name "Removing Beta" --description "Bumping Alpha and disabling Beta"
In this release, only the provided plugins are added to this release's configuration. The end result will be that only plugin-alpha
is enabled.
The --new
argument must be used if you are disabling a plugin that is on the active configuration.
The Flex Plugins CLI uses your Twilio Account SID and Auth Token to deploy your plugins.
If you are deploying your plugins to multiple accounts, you will need to provide credentials for each account. You can create multiple profiles using the Twilio CLI to store multiple credentials, and then pass them through to your commands in a few ways:
Let's say you have created a profile called stage
. You can pass the profile name in the deploy
command to use the designated account.
_10twilio flex:plugins:deploy -p stage
Alternatively, you may switch which profile is active using the Twilio CLI's profiles
command. To see the full list of local profiles and choose a new active profile, run:
_10twilio profiles:list_10twilio profiles:use PROFILE_ID
New pairs of AccountSid and AuthToken credentials may also be provided as environment variables with the deploy
command:
_10TWILIO_ACCOUNT_SID=ACxxx TWILIO_AUTH_TOKEN=abc123 twilio flex:plugins:deploy
This will use the provided credentials and save them in the keychain. If you have multiple accounts saved and you do not provide credentials along with your deploy
command, then you will be prompted to select one:
_10? Select from one of the following Account Sids (Use arrow keys)_10❯ AC0000000000000000000000000000000_10 AC0000000000000000000000000000001_10 AC0000000000000000000000000000002
You can use the above commands to tie plugin deployment into a CI/CD pipeline. For example:
_10# !/bin/bash_10# This script runs within your plugin directory_10npm install_10npm run test_10npm run lint_10TWILIO_ACCOUNT_SID=ACXXXX TWILIO_AUTH_TOKEN=pass123 twilio flex:plugins:deploy
Make sure to handle your AccountSid and Auth Token as environment variables or arguments passed into your scripts.