Allow overrides for cascading instance level settings

Allow overrides for cascading settings

Problem

Currently, there is no way to override instance-level cascading settings at the project level. This prevents customers from exempting specific projects from instance-wide configurations.

Use Case

A customer (Internal ticket) wants to exempt one project from the instance-level push rule setting that prevents approvals by users who add commits. Currently, this is not possible due to the cascading nature of the setting.

Proposed Solution

Implement override functionality for cascading settings, similar to the approach in the closed MR: !148271 (closed)

This would allow project administrators to override specific instance-level settings when needed, providing more flexibility in configuration management while maintaining the benefits of centralized defaults.

Acceptance Criteria

  • Project-level overrides can be configured for cascading settings
  • Override functionality works specifically for push rule settings
  • Changes are backward compatible with existing configurations
  • Appropriate permissions are enforced for override capabilities

Description was generated using AI

Edited by 🤖 GitLab Bot 🤖