drupal-config-mgmt
Drupal Configuration Management
Comprehensive guide for Drupal configuration management including imports, exports, config splits, and environment syncing.
Remote CLI — host-neutral
Examples below use Pantheon's Terminus (terminus drush <site>.<env> -- <cmd>). The commands are identical on any host — substitute your platform's remote-drush form. If your platform provides Drush site aliases, the generic drush @<alias> <cmd> works everywhere.
| Task | Acquia (acli) |
Pantheon (Terminus) | Platform.sh / Upsun | Lagoon (amazee.io) | Generic (Drush aliases) |
|---|---|---|---|---|---|
| Remote drush | acli remote:drush -- <cmd> |
terminus drush <site>.<env> -- <cmd> |
platform drush -e <env> -- <cmd> (Upsun: upsun drush …) |
lagoon ssh -p <project> -e <env> -C "drush <cmd>" |
drush @<alias> <cmd> |
| Get/inspect config | acli remote:drush -- config:get <name> |
terminus drush <site>.<env> -- config:get <name> |
platform drush -e <env> -- config:get <name> |
lagoon ssh -p <project> -e <env> -C "drush config:get <name>" |
drush @<alias> config:get <name> |
The auto-confirm warning below applies to every host — append
--notocim/config:importto preview instead of apply. Drush defaults to--yeswhen invoked non-interactively (which all remote-CLI wrappers do).
Problem: Avoid Accidental Config Imports
CRITICAL: Terminus drush commands default to --yes unless explicitly told --no. This means commands like config:import or cim will AUTO-CONFIRM and import configuration even when you only want to inspect differences.