Importing packages on Acquia Cloud

To deploy your Site Studio packages alongside Drupal configuration you may want to utilise Acquia Cloud hooks to perform import operations during code changes.

Import full package

Example:

drush @$site'.'$target_env updatedb --no-cache-clear -y
drush @$site'.'$target_env cache:rebuild
drush @$site'.'$target_env cim -y
drush @$site'.'$target_env sync:import --overwrite-all --force 
drush @$site'.'$target_env cache:rebuild

Import individual packages

Example:

drush @$site'.'$target_env updatedb --no-cache-clear -y
drush @$site'.'$target_env cache:rebuild
drush @$site'.'$target_env cim -y 
drush @$site'.'$target_env sync:import --path=path/to/package/dir --overwrite-all --force
drush @$site'.'$target_env sync:import --path=path/to/other-package/dir --overwrite-all --force
drush @$site'.'$target_env cache:rebuild

 

Import and Upgrade

When upgrading between versions or when installing Site Studio for the first time; additional commands should also be run (see: Upgrading Site Studio)

Example:

# Run Drupal database updates
drush @$site'.'$target_env updatedb --no-cache-clear -y
drush @$site'.'$target_env cache:rebuild

# Import Drupal configuration
# - Site Studio packages are excluded via config split.
drush @$site'.'$target_env cim -y 

# Import Site Studio UI assets for this version
drush @$site'.'$target_env cohesion:import

# Import individual package 1
drush @$site'.'$target_env sync:import --path=path/to/package/dir --overwrite-all --force
# Import individual package 2
drush @$site'.'$target_env sync:import --path=path/to/other/package/dir --overwrite-all --force

# Run a full Site Studio rebuild when upgrading
drush @$site'.'$target_env cohesion:rebuild

drush @$site'.'$target_env cache:rebuild

 

 

Additional parameters are available in Site Studio version 6.4 and above to optimise the import process.