Skip to content

Adds backend project setting for model registry

Darby Frey requested to merge model-registry-feature-setting into master

What does this MR do and why?

This MR addresses the first part of Add feature toggle for Model registry (#412734 - closed) by adding the attribute to the database and the configuration for the Model Registry feature setting.

How to set up and validate locally

  1. Run migrations
  2. on rails console, run the command below. It should return 20 
    Project.first.model_experiments_access_level

Database Review

Up 
main: == [advisory_lock_connection] object_id: 184060, pg_backend_pid: 11065
main: == 20231130195635 AddModelRegistryAccessLevelToProjectFeature: migrating ======
main: -- add_column(:project_features, :model_registry_access_level, :integer, {:null=>false, :default=>20})
main:    -> 0.0026s
main: == 20231130195635 AddModelRegistryAccessLevelToProjectFeature: migrated (0.0062s) 

main: == [advisory_lock_connection] object_id: 184060, pg_backend_pid: 11065
Down 
main: == [advisory_lock_connection] object_id: 184060, pg_backend_pid: 10462
main: == 20231130195635 AddModelRegistryAccessLevelToProjectFeature: reverting ======
main: -- remove_column(:project_features, :model_registry_access_level, :integer, {:null=>false, :default=>20})
main:    -> 0.0026s
main: == 20231130195635 AddModelRegistryAccessLevelToProjectFeature: reverted (0.0087s) 

main: == [advisory_lock_connection] object_id: 184060, pg_backend_pid: 10462

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports