Package import using drush

The Site Studio Sync sub module provides an import command that allows package imports from specified or default location. Both individual and full packages are supported:

$ drush sync:import

This command has the following options:

• --overwrite-all - Overwrite existing entities when differences detected
• --keep-all - Keep any existing entities when differences detected
• --path[=PATH] - Specify path to a directory containing package files. If this option is omitted, command defaults to value set in $settings['site_studio_sync'].
• --force - Force importing entities even if this will break content (eg. skip validation warnings)
• --no-rebuild - Do not run a rebuild operation as part of the import process, useful if you are upgrading and plan to run cohesion:rebuild in a subsequent command
• --no-maintenance - Skip the default step whereby the site is put into maintenance mode during the import process, useful when performing an import on Site Factory where sites are already placed in and out of maintenance mode.

Example

To import all previously exported *.package.yml_ files from your sync directory into the current site, use the following drush command:

$ drush sync:import --overwrite-all

 

Example

To deploy a specific *.package.yml file via drush, you can specify a local or remote file path like this:

$ drush sync:import --path=/path/to/local.package.yml --overwrite-all

$ drush sync:import --path=http://domain.com/remote.package.yml --overwrite-all

 

For further examples on how to utilise these commands when importing packages into an Acquia cloud environment see: Importing packages on Acquia Cloud