Webform configs still get exported on running drush export

Created on 30 September 2022, about 2 years ago
Updated 21 December 2023, about 1 year ago

Problem/Motivation

With this module enabled, drush export command should ignore the webform configs. But, it exports webforms and webform options.

Steps to reproduce

  1. Enable Webform config ignore module.
  2. Make changes in a webform.
  3. Run drush cex and observe the config file changes. It exports all the webforms along with webform options files.

Proposed resolution

Similar to Config Ignore, it should support filtering via Drush.

🐛 Bug report
Status

Needs work

Version

1.2

Component

Code

Created by

🇮🇳India psingh10

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇩🇪Germany cweiske

    We use webform_config_ignore to not run into problems when deploying code to a test/stage/production system that has changed webform configuration in the database.

    Our process is:

    1. Get a new database dump from live
    2. Import it locally
    3. Import the local configuration that is committed into git
    4. Export the (webform) changes and commit it to git, so that we have the current state in version control

    This would break when the export would ignore webforms completely. So I'm on bburg's side, and would like to keep the current behavior.

  • 🇺🇸United States robpowell Boston

    I'll add that I agree with the OP and this is how I expected it to work. Ignoring config should do just that, ignore them fully. In terms of a patch approach to provide this functionality, we could have a config option that a user could opt in to fully ignore the config.

Production build 0.71.5 2024