Standardize Config Ignore

Created on 9 March 2023, over 1 year ago
Updated 14 March 2023, over 1 year ago

Problem/Motivation

Common occurrence on D8/9/10 is that someone makes a change to something on the live site that is managed by the Config Management system, but debatably should've been set up with the State system, or something else.

Steps to reproduce

  • Move standard menu items around (changes core.menu.static_menu_link_overrides)
  • In the Redirect 404s report, mark a 404 as "ignore" (changes redirect_404.settings)
  • Change the homepage to a new node (on pages that use a "homepage" content type, changes system.site:page.front)
  • Add a "Domain" redirect via the Domain Redirect submodule (changes redirect_domain.domains)

Proposed resolution

In Sous, include default config_ignore:

➜ cat config_ignore.settings.yml
_core:
  default_config_hash: UVH1aJ4b44UM-VdPVN7hNNuuVqfReJxwfVeDQH1Hvsk
ignored_config_entities:
  - redirect_404.settings
  - redirect_domain.domains
  - core.menu.static_menu_link_overrides
  - 'system.site:page.front'

Remaining tasks

TBD

✨ Feature request
Status

Active

Version

5.0

Component

Code

Created by

πŸ‡¨πŸ‡¦Canada dalin Guelph, πŸ‡¨πŸ‡¦, 🌍

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

Comments & Activities

Production build 0.69.0 2024