Resolving Configuration Verifier Deltas

After you run the Configuration Verifier (CV), review all reported delta definitions. Resolve these deltas before deploying new project configurations to production or when validating a local upgrade using a copy of the production repository.

How to Resolve a Delta Definition

For each delta definition reported by CV, determine its category and take the appropriate action:

• Intended Configuration Changes
  If the delta results from an intentional update or upgrade to your configuration, add the delta definition path to the ignorepaths section in your configuration-verifier-config.yaml file.

• Runtime Changes

  • Configuration Changes
    • If you want to keep the runtime change, update your project's configuration definitions to include this change. Run CV again to confirm the delta is resolved.
    • If you do not want to keep the runtime change, add the path to the ignorepaths section in your configuration-verifier-config.yaml file.
  • Content Changes
    If the delta is reported as content, the configuration model still treats the node(s) as configuration. To correct this, add .meta:category: content or .meta:residual-child-node-category: content to your project's configuration definitions for the parent node of the delta. Run CV again to verify the delta is no longer reported.
  • System Changes
    If the delta is reported as a system change, the configuration model still treats the node or property as configuration. Add .meta:category: system or .meta:residual-child-node-category: system to your project's configuration definitions for the relevant node or property. Run CV again to confirm the delta is resolved.