Frontend: Display the total number of variables and limit
Summary
We have limits to the number of variables that can be defined at the instance level. For organizations which lean heavily on the use of variables, it is important for the GitLab administrators to know 1) how many variables are defined and 2) if they are approaching their limit.
Why this matters and how we measure
We should add instrumentation to understand the average number of variables per instance/group/project. We typically do not recommend more than 200 variables be defined for each project/group for optimal performance and in %15.7 we created this limit, however, existing projects with over 200 variables are "locked in" to the higher number of variables.
User Stories
Proposal
Something simple meets this need; text at the top of the variables table is one option with a reminder of the 200 variables limit.
Performance Considerations
Out of Scope
Advanced warning features such as the user of colors or other visual treatment to identify the number of variables is out of scope, as well as changes to pagination (i.e. "Showing 41-60 of 173 variables").
Acceptance Criteria
Additional details
Some relevant technical details, if applicable, such as:
- Does this need a feature flag?
- Does there need to be an associated instrumentation issue created related to this work?
- Is there an example response showing the data structure that should be returned (new endpoints only)?
- What permissions should be used?
- Which tier(s) is this for?
- Additional comments:
Implementation Table
Group | Issue Link |
---|---|
backend | Issue Title |
frontend |
|
documentation | Issue Title |
Instrumentation | Issue Title |