PHPackages                             pantheon-quicksilver/drush-config-import - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. pantheon-quicksilver/drush-config-import

ActiveQuicksilver-script[Utility & Helpers](/categories/utility)

pantheon-quicksilver/drush-config-import
========================================

Importing drupal configuration changes from .yml files with drush.

117.7k↓50%PHP

Since Oct 28Pushed 4y ago1 watchersCompare

[ Source](https://github.com/pantheon-quicksilver/drush-config-import)[ Packagist](https://packagist.org/packages/pantheon-quicksilver/drush-config-import)[ RSS](/packages/pantheon-quicksilver-drush-config-import/feed)WikiDiscussions main Synced 1mo ago

READMEChangelogDependenciesVersions (2)Used By (0)

Configuration import
====================

[](#configuration-import)

This example will show you how to integrate Drush commands into your Quicksilver operations, with the practical outcome of importing configuration changes from `.yml` files . You can use the method shown here to run any Drush command you like.

Note that with the current `webphp` type operations, your timeout is limited to 120 seconds, so long-running operations should be avoided for now.

Requirements
------------

[](#requirements)

While these scripts can be downloaded individually, they are meant to work with Composer. See the installation in the next section.

- Quicksilver script projects and the script name itself should be consistent in naming convention.
- README should include a recommendation for types of hooks and stages that the script should run on.
    - For example, "This script should run on `clone_database` and the `after` stage.
    - Provide a snippet that can be pasted into the `pantheon.yml` file.

### Installation

[](#installation)

This project is designed to be included from a site's `composer.json` file, and placed in its appropriate installation directory by [Composer Installers](https://github.com/composer/installers).

In order for this to work, you should have the following in your composer.json file:

```
{
  "require": {
    "composer/installers": "^1"
  },
  "extra": {
    "installer-paths": {
      "web/private/scripts/quicksilver": ["type:quicksilver-script"]
    }
  }
}
```

The project can be included by using the command:

`composer require pantheon-quicksilver/drush-config-import:^1`

If you are using one of the example PR workflow projects ([Drupal 8](https://www.github.com/pantheon-systems/example-drops-8-composer), [Drupal 9](https://www.github.com/pantheon-systems/drupal-project), [WordPress](https://www.github.com/pantheon-systems/example-wordpress-composer)) as a starting point for your site, these entries should already be present in your `composer.json`.

Note that automating this step may not be appropriate for all sites. Sites on which configuration is edited in the live environment may not want to automatically switch to configuration stored in files. For more information, see

Optionally, you may want to use the `terminus workflow:watch` command to get immediate debugging feedback.

### Example `pantheon.yml`

[](#example-pantheonyml)

Here's an example of what your `pantheon.yml` would look like if this were the only Quicksilver operation you wanted to use:

```
api_version: 1

workflows:
  deploy:
    after:
      - type: webphp
        description: Import configuration from .yml files
        script: private/scripts/quicksilver/drush-config-import/drush-config-import.php
```

###  Health Score

23

—

LowBetter than 27% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity27

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity30

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/1759794?v=4)[Kyle Taylor](/maintainers/kyletaylored)[@kyletaylored](https://github.com/kyletaylored)

---

Top Contributors

[![namespacebrian](https://avatars.githubusercontent.com/u/87093053?v=4)](https://github.com/namespacebrian "namespacebrian (2 commits)")

### Embed Badge

![Health badge](/badges/pantheon-quicksilver-drush-config-import/health.svg)

```
[![Health](https://phpackages.com/badges/pantheon-quicksilver-drush-config-import/health.svg)](https://phpackages.com/packages/pantheon-quicksilver-drush-config-import)
```

###  Alternatives

[xajax/xajax

Xajax is an open source PHP class library for easily creating powerful PHP-driven, web-based Ajax Applications. Using Xajax, you can asynchronously call PHP functions and update the content of your your webpage without reloading the page.

20710.7k](/packages/xajax-xajax)[mpociot/reanimate

Undo Laravel soft deletes

1221.2k](/packages/mpociot-reanimate)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)