Skip to content

Add entry to 'plans' for the new Ultimate Trial

Paulo Barros requested to merge pb/cdot-7380/create-new-ultimate-trial-plan into master

This is part of customers-gitlab-com#7380 (closed).

What does this MR do and why?

This MR adds a migration which creates a new entry to the plans table to support the upcoming Ultimate trial plan for paid customers. We want to be able to configure and track those trials separately from the current Ultimate trial tier.

The plans table is a very small table with only 10 entries at the time of writing.

Screenshots or screen recordings

N/A

How to set up and validate locally

Run the migrations.

Up

❯ bin/rails db:migrate VERSION=20231030154117
main: == [advisory_lock_connection] object_id: 180460, pg_backend_pid: 2784
main: == 20231030154117 InsertNewUltimateTrialPlanIntoPlans: migrating ==============
main: == 20231030154117 InsertNewUltimateTrialPlanIntoPlans: migrated (0.0506s) =====

main: == [advisory_lock_connection] object_id: 180460, pg_backend_pid: 2784
ci: == [advisory_lock_connection] object_id: 180660, pg_backend_pid: 2786
ci: == 20231030154117 InsertNewUltimateTrialPlanIntoPlans: migrating ==============
ci: -- The migration is skipped since it modifies the schemas: [:gitlab_main].
ci: -- This database can only apply migrations in one of the following schemas: [:gitlab_ci, :gitlab_internal, :gitlab_shared].
ci: == 20231030154117 InsertNewUltimateTrialPlanIntoPlans: migrated (0.0187s) =====

ci: == [advisory_lock_connection] object_id: 180660, pg_backend_pid: 2786

Down

❯ bin/rails db:rollback:main
main: == [advisory_lock_connection] object_id: 180120, pg_backend_pid: 3896
main: == 20231030154117 InsertNewUltimateTrialPlanIntoPlans: reverting ==============
main: == 20231030154117 InsertNewUltimateTrialPlanIntoPlans: reverted (0.0445s) =====

main: == [advisory_lock_connection] object_id: 180120, pg_backend_pid: 3896

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