Skip to content

Add force_include_all_resources field to workspaces

What does this MR do and why?

Add force_include_all_resources field to workspaces

Related to #425745 (closed)

Migration output

$ bin/rails db:migrate:up:main VERSION=20230920162613 RAILS_ENV=development
main: == [advisory_lock_connection] object_id: 227080, pg_backend_pid: 584085
main: == 20230920162613 AddForceIncludeAllResourcesToWorkspaces: migrating ==========
main: -- add_column(:workspaces, :force_include_all_resources, :boolean, {:default=>false, :null=>false})
main:    -> 0.0033s
main: == 20230920162613 AddForceIncludeAllResourcesToWorkspaces: migrated (0.0085s) =

main: == [advisory_lock_connection] object_id: 227080, pg_backend_pid: 584085


$ bin/rails db:migrate:down:main VERSION=20230920162613 RAILS_ENV=development
main: == [advisory_lock_connection] object_id: 227160, pg_backend_pid: 584517
main: == 20230920162613 AddForceIncludeAllResourcesToWorkspaces: reverting ==========
main: -- remove_column(:workspaces, :force_include_all_resources, :boolean, {:default=>false, :null=>false})
main:    -> 0.0128s
main: == 20230920162613 AddForceIncludeAllResourcesToWorkspaces: reverted (0.0180s) =

main: == [advisory_lock_connection] object_id: 227160, pg_backend_pid: 584517

MR acceptance checklist

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

Edited by Alper Akgun

Merge request reports