Announce deprecation of custom geo:db:* rake tasks
For guidance on the overall deprecations, removals and breaking changes workflow, please visit https://about.gitlab.com/handbook/product/gitlab-the-product/#breaking-changes-deprecations-and-removing-features
Deprecation Summary
In %14.8, we are replacing the geo:db:* rake tasks with built-in tasks that are now possible after switching the Geo tracking database to use Rails 6 many databases support.
We will announce deprecation for these tasks in %14.8 with removal planned for %15.0.
Breaking Change
The following geo:db:* tasks will be replaced with corresponding db:*:geo tasks:
-
geo:db:drop->db:drop:geo -
geo:db:create->db:create:geo -
geo:db:setup->db:setup:geo -
geo:db:migrate->db:migrate:geo -
geo:db:rollback->db:rollback:geo -
geo:db:version->db:version:geo -
geo:db:reset->db:reset:geo -
geo:db:seed->db:seed:geo -
geo:schema:load:geo->db:schema:load:geo -
geo:db:schema:dump->db:schema:dump:geo -
geo:db:migrate:up->db:migrate:up:geo -
geo:db:migrate:down->db:migrate:down:geo -
geo:db:migrate:redo->db:migrate:redo:geo -
geo:db:migrate:status->db:migrate:status:geo -
geo:db:test:prepare->db:test:prepare:geo -
geo:db:test:load->db:test:load:geo -
geo:db:test:purge->db:test:purge:geo
Affected Topology
Self-Managed customers using Geo
Affected Tier
- Premium
- Ultimate
Checklist
-
@mention your stage's stable counterparts on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager. - To see who the stable counterparts are for a product team visit product categories
- If there is no stable counterpart listed for Sales/CS please mention
@timtams - If there is no stable counterpart listed for Support please @mention
@gitlab-com/support/managers - If there is no stable counterpart listed for Marketing please mention
@cfoster3
- If there is no stable counterpart listed for Sales/CS please mention
- To see who the stable counterparts are for a product team visit product categories
-
@mention your GPM so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change.