Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • C cloud-config-server
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Redmine
    • Redmine
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cloud configurations
  • cloud-config-server
  • Merge requests
  • !5

Merged
Created Oct 22, 2026 by Andres Rueda@andresRuedaDeveloper

config(ech-cms): declare asset content validation REPORT_ONLY rollout mode

  • Overview 0
  • Commits 1
  • Changes 2

Purpose

Make the initial secure-asset-content-validation rollout mode explicit for ECH CMS.

Changes

  • Set ech.assets.content-validation.mode: REPORT_ONLY in ech-cms-ech07.yml and ech-cms-docker.yml.
  • Do not enable ENFORCE or change policy mappings, limits, or versions.

Validation

  • Both YAML files parse and resolve the property to REPORT_ONLY.
  • git diff --check passes.
  • The effective value in ECH07 has not yet been verified; that requires deployment and a configuration-binding/startup check.

Deployment task — environments without a public Config Server

Configure ech.assets.content-validation.mode=REPORT_ONLY in each environment's private configuration source before restarting or refreshing ECH CMS. Verify and record the effective loaded value per environment; do not infer it from the application default or this repository. A later move to ENFORCE requires its separate rollout evidence and approval. Roll back the mode to REPORT_ONLY if needed; this does not reverse schema or other non-flagged changes.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: feature/secure-asset-content-validation-rollout-config