Use separate rate limiter for deploy keys portion of AutocompleteController
Background
See this Epic for context
Proposal
Create a separate rate limited for the deploy keys portion of AutocompleteController. Currently, these are all combined and are conflicting with each other for functions that are not related, resulting in users hitting rate limits upon autocomplete when they shouldn't.
Designs
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Hannah Sutor added to epic &13727
added to epic &13727
- Maintainer
@hsutor, Please add a group or category label to identify issue ownership.You can refer to the Features by Group handbook page for guidance.
If you are unsure about the correct group, please do not leave the issue without a group label, and refer to GitLab's shared responsibility functionality guidelines for more information on how to triage this kind of issue.
This message was generated automatically. You're welcome to improve it.
- Hannah Sutor changed the description
Compare with previous version changed the description
- Hannah Sutor added groupenvironments typemaintenance labels
added groupenvironments typemaintenance labels
- 🤖 GitLab Bot 🤖 added devopsdeploy sectioncd labels
added devopsdeploy sectioncd labels
- Hannah Sutor changed the description
Compare with previous version changed the description
- Author Developer
@nagyv-gitlab FYI, just created this as a result of this discussion. AFAIK, this is not urgent and can stay in the backlog.
1 - Hannah Sutor changed the description
Compare with previous version changed the description
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#17607 (closed)
mentioned in issue gitlab-org/quality/triage-reports#17607 (closed)
- Viktor Nagy (GitLab) added environmentsparked label
added environmentsparked label
- Viktor Nagy (GitLab) changed milestone to %Backlog
changed milestone to %Backlog
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#17709 (closed)
mentioned in issue gitlab-org/quality/triage-reports#17709 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#17794 (closed)
mentioned in issue gitlab-org/quality/triage-reports#17794 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#17900 (closed)
mentioned in issue gitlab-org/quality/triage-reports#17900 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#18065 (closed)
mentioned in issue gitlab-org/quality/triage-reports#18065 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#18164 (closed)
mentioned in issue gitlab-org/quality/triage-reports#18164 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#18246 (closed)
mentioned in issue gitlab-org/quality/triage-reports#18246 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#18353 (closed)
mentioned in issue gitlab-org/quality/triage-reports#18353 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#18437 (closed)
mentioned in issue gitlab-org/quality/triage-reports#18437 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#18633 (closed)
mentioned in issue gitlab-org/quality/triage-reports#18633 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#18718 (closed)
mentioned in issue gitlab-org/quality/triage-reports#18718 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#18802 (closed)
mentioned in issue gitlab-org/quality/triage-reports#18802 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#18913 (closed)
mentioned in issue gitlab-org/quality/triage-reports#18913 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19083 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19083 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19194 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19194 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19283 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19283 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19367 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19367 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19538 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19538 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19653 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19653 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19665 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19665 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19802 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19802 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19912 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19912 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19992 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19992 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#20125 (closed)
mentioned in issue gitlab-org/quality/triage-reports#20125 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#20243 (closed)
mentioned in issue gitlab-org/quality/triage-reports#20243 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#20325 (closed)
mentioned in issue gitlab-org/quality/triage-reports#20325 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#20441 (closed)
mentioned in issue gitlab-org/quality/triage-reports#20441 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#20578 (closed)
mentioned in issue gitlab-org/quality/triage-reports#20578 (closed)