Deprecate Legacy Gitaly Configuration Methods

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

Gitaly will be deprecating two legacy variables that were originally used to configure Gitaly:

• GIT_CONFIG_SYSTEM
• GIT_CONFIG_GLOBAL

These variables are being deprecated in favor of utilizing the standard config.toml file for Gitaly as documented in the Gitaly Reference section of our documentation.

Breaking Change

Any users which are presently using the legacy variables mentioned above will need to update to a standard configuration method as described in our documentation.

Affected Topology

This only impacts self-hosted users.

Affected Tier

This impacts all self-hosted instances regardless of tier.

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

• @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.

Deprecation Milestone

We will begin announcing the deprecation in %14.8.

Planned Removal Milestone

We are planning on removing support in %15.0.

Links

Configuration Documentation - https://docs.gitlab.com/ee/administration/gitaly/configure_gitaly.html Gitaly Issue - gitaly#3617 (closed)