Either limit or disable Gitaly calls per Rails action

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

As GitLab codebase abstractions grows we're more eager to use classes that make Gitaly calls and returns data that we don't necessarily need, which is a subject being discussed for TODOs #39509 (closed).

For DB, we got Gitlab::QueryLimiting for limiting the amount of calls. I wonder if we shouldn't follow that path for Gitaly as well, allowing to either limit or even block Gitaly calls, raising errors on test and development environments and whitelisting where needed with issues per action.

That should bring some awareness for consuming Gitaly.

Edited Jul 03, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading