Thank you. Thank you. For this awesome module. Development has become easier and less irritating again with this module. Thank you for the time and effort. This is a quality developer friendly module. Good job!

Problem/Motivation

We have a requirement in a project that the CI should not deploy if someone has changed a config on the instance. We are using Drush 9 and I have this in my .gitlab-ci.yml

  script:
    - config_status=$(ssh user@machine.com 'cd www/project/web && drush cst')
    - if [[ $config_status = *"Different"* || $config_status = *"Only in"* ]]; then
    - echo "Hold on! Somebody has changed the configuration."
    - exit 1
    - fi

This is so far working alright. The problem is drush cst is also showing the ignored configs. Looks like this module is not respecting the ignored configs while showing the configuration status.

Proposed resolution

Not yet decided.

Remaining tasks

Not yet decided.

User interface changes

Not yet decided.

API changes

Not yet decided.

Data model changes

Not yet decided.

Comments

subhojit777 created an issue. See original summary.

subhojit777’s picture

subhojit777
he/him
Primary language Bengali
commented
Issue summary: View changes
bircher’s picture

bircher
Location 🇨🇿
commented

Thanks for the compliments, it solved a need we had and it seems a lot of other developers had it too.

I don't have drush 9 handy right now, so I can't verify right now what is shown. but it should show exactly the same as the config import page in the drupal admin ui.

If you have a production split that should hold the allowed changes you should do a drush csex production first to make a "backup" of the split. ie you update that split by exporting only it and then the status should be "no changes".

config_split is about making sure there is no surprises, so importing still means "as the combined directories" contain. if you want to ignore some config you can use config_ignore it allows you to configure some config as "never update" so be careful...