Frontend: Audit history for CI Variables
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
Often times, more than one user has permissions to add/update/delete variables. There is no way today for other team members to understand:
- Was the value of the variable updated - and when?
- Was a variable deleted?
- Is a variable still required (e.g. it has not been used in over a year)?
These are all questions which can help a team understand:
- Potential failures in a pipeline due to variable value changes
- Opportunities for clean up, as there is a finite limit for the number of variables that can be defined.
Why this matters and how we measure
In alignment with
User Stories
Proposal
Performance Considerations
Out of Scope
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 |
|
| frontend | Issue Title |
| documentation | Issue Title |
| Instrumentation | Issue Title |
Links/References
Edited by 🤖 GitLab Bot 🤖