Discussion: Badges management for CI Catalog
Summary
From a discussion in https://gitlab.slack.com/archives/C03RZTZ59QE/p1712916414399759, we're moving our thoughts to this issue to discuss further for thoughts on how badge management makes sense going forward.
Proposal
Right now, the steps will be as follows:
- create the service so [someone] can run the command
- find someone to run the command for google/gitlab (so just twice)
- determine what the process is going forward
👈 WE ARE HERE FOR THIS DISCUSSION
- we need to know how many requests we are expecting to have to find a solution, since doing a UI solution might be too much
Confirm purpose and User Reception (how does this benefit the user?)
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?
- Is this EE or CE?
-
EE -
CE
-
- Additional comments:
Links/References
Edited by Mark Nuzzo