Pipeline editor incorrectly shows "Missing CI config file" validation errors when PEP with override_project_ci is enabled

Summary

When a Pipeline Execution Policy (PEP) with pipeline_config_strategy: override_project_ci is enabled at the top-level group, the Pipeline Editor displays incorrect validation errors across all tabs (Edit, Visualize, Validate, Full Configuration) when editing any project’s .gitlab-ci.yml where PEP is applied. Pipelines run correctly, but the UI incorrectly reports that the CI configuration is missing or invalid. The errors are misleading and create confusion about whether the configuration is actually valid.

Steps to reproduce

  1. Create and enable a Pipeline Execution Policy at the group level using pipeline_config_strategy: override_project_ci.
  2. Go to any project in the policy scope and open the Pipeline Editor.
  3. Edit the .gitlab-ci.yml file.
  4. Observe the UI showing an error This GitLab CI configuration is invalid: Missing CI config file

What is the expected correct behavior?

  • The Pipeline Editor should load and render the project’s .gitlab-ci.yml normally, even when the PEP overrides CI configuration.
  • If the policy affects or replaces the project config, the UI should show a non-blocking warning, not an error.
  • Visualize, Validate, and Full Configuration tabs should display merged configuration or an appropriate fallback view.

Relevant logs and/or screenshots

image.png

image.png

image.png

Additional context

  • Affects all projects under the group where the PEP is enabled.
  • Despite the errors, any commits made to the yaml config are applied and reflected. Pipelines run successfully despite the UI errors, this appears to be a UI/UX validation issue.
  • Issue is consistently reproducible.
  • The problem does not occur when using pipeline_config_strategy: inject_policy.
Edited by 🤖 GitLab Bot 🤖