Draft: Support runner cost factor fields through Rest API
What does this MR do and why?
Runner cost factors are a GitLab.com feature for now and until now we've been managing them by hand through the UI. With the growth of the scale of our Hosted Runners for GitLab.com, this approach is no more easy nor nice to use. We want to automate it a little, but for that we need to expose access to the cost factor fields through the API.
References
Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.