Pantheon's Autopilot:

• Automatically detects when new updates are available
• Performs the updates in an isolated Multidev environment
• Tests the updates with automated visual regression testing (VRT)
• Optionally deploys the updates

You can perform comprehensive Autopilot functions through your Dashboard. Refer to the Autopilot guide for more information.

Review the Autopilot Site Compatibility documentation on Pantheon to ensure that your site is compatible with Autopilot.

The Terminus Autopilot plugin is available for Early Access participants. Features for the Terminus Autopilot plugin are in active development. Pantheon's development team is rolling out new functionality often while this product is in Early Access. Visit the Pantheon Slack channel (or sign up for the channel if you don't already have an account) to learn how you can enroll in our Early Access program. Please review Pantheon's Software Evaluation Licensing Terms for more information about access to our software.

Autopilot requires the following:

• A site with Autopilot available
• Terminus 3

The Terminus Autopilot plugin does not currently provide the following functionality:

• Selection of specific modules, themes, or Custom Upstreams for updates
• Management of excluded updates

Run the command below to install the Terminus Autopilot plugin.

terminus self:plugin:install terminus-autopilot-plugin

This section provides currently supported commands for the Terminus Autopilot plugin.

You can activate for deactivate Autopilot for a specific site name or ID.

To activate a site:

site:autopilot:activate {SITE_NAME|SITE_ID}

To deactivate a site:

site:autopilot:deactivate {SITE_NAME|SITE_ID}

You can use the command below to get the destination environment in which Autopilot is currently running.

site:autopilot:deployment-destination {SITE_NAME|SITE_ID}

You can use the command below to set the destination environment for Autopilot.

site:autopilot:deployment-destination {SITE_NAME|SITE_ID} {{ENV}}

You can explicitly set environment syncing. This syncs the target Autopilot environment to the Live environment before applying updates in an Autopilot cycle.

To enable environment syncing:

site:autopilot:env-sync:enable

To disable environment syncing:

site:autopilot:env-sync:disable

You can use the command below to set the frequency at which Autopilot runs. Valid options are:

• daily (for Platinum sites and above)
• weekly
• monthly
• manual

site:autopilot:frequency