Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 56.6k
    • Issues 56.6k
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1.8k
    • Merge requests 1.8k
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Tracing
    • Incidents
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #321724
Closed
Open
Issue created Feb 16, 2021 by Melissa Ushakov@mushakov🌻Developer

Cascading Settings - Make POC Production Ready

Release notes

Problem to solve

In issue #291082 (closed) we implemented a POC for cascading settings from a group to all subgroups below it. This issue will track the work needed to make this feature production-ready. The first setting we will support is delayed project deletion.

Proposal

Complete hardening of the feature for GA release

See !51498 (closed) for backend POC. The code is not quite production ready.

  • Migrations were messy and need to be updated after !53916 (merged) is merged.
  • Needs tests.
  • Needs developer documentation on using lockable_attrs and the associated database migrations (lock column, can be null, etc).
  • Document CascadingNamespaceAttribute so the code is clear to future developers. Since it's a bit of meta-programming it can be difficult to understand at first.

Parent group

Screen_Shot_2021-03-26_at_1.10.44_PM

Child group

Screen_Shot_2021-03-30_at_9.48.33_AM

Edited Mar 31, 2021 by Daniel Mora
Assignee
Assign to
Time tracking