snipper

Does your team ever need to apply just one configuration change — without triggering a full sync that pulls in everything else that is staged? Snipper gives developers and site builders per-item control over configuration, directly from the synchronization page.

When a site uses the standard Configuration Synchronization workflow, every import is all-or-nothing. That works great for deployments, but it creates friction during development: one fix is ready, forty others are not. Or a setting was tweaked in the UI and needs to be captured back to the sync directory before the next deployment overwrites it. Snipper solves this by adding Import, Export, and Download YML operation links to every item listed on the Configuration Synchronization page — right next to the existing "View differences" link. No separate page, no copy-pasting YAML, no Drush command required.

How it works

1. Navigate to Administration > Configuration > Development > Configuration synchronization.
2. Each listed configuration item now shows additional operation links alongside "View differences".
3. Click Import to write that single item from the sync directory into the active (database) configuration.
4. Click Export to write the active version of that item back to the sync directory.
5. Click Download YML to immediately download the item as a .yml file.

Features

• Import single item — apply one staged change without touching anything else
• Export single item — capture a UI change back to the sync directory on the spot
• Download YML — get the raw YAML of any differing item in one click, no Drush needed
• Collection support — works with language and other configuration collections
• Confirmation step — Import and Export show a confirm page before making any change
• Zero configuration — install, enable, done

Requirements

• Drupal 10 or 11
• Core config module (enabled by default)

Note: Import and Export write directly to the active or sync storage without running the full ConfigImporter pipeline. Hooks, validators, and dependency ordering are not invoked. These operations are best suited for individual settings, fields, views, and display modes — not for enabling or disabling modules or themes.