<!-- ## Implementation Issue To-Do list (_NOTE: This section can be removed when the issue is ready for creation_) - [ ] Ensure that issue title is concise yet descriptive - [ ] Add `Frontend :` or `Backend: ` per group [naming conventions](https://about.gitlab.com/handbook/engineering/development/ops/verify/pipeline-authoring/#splitting-issues) - [ ] Ensure the issue containing the feature or change proposal and related discussions is linked as related to this implementation issue. - [ ] Aside from default labeling, please make sure to include relevant labels for `type::`, `workflow::`, and `gitlab~3412464`/`gitlab~2492649` labeling. - [ ] Issues with user-facing changes should include the `gitlab~2024184` label. --> ## Summary This issue is related to the discussion in step 4 of https://gitlab.com/gitlab-org/gitlab/-/issues/362262#proposal where a user is allowed to assign names to the various settings through the configuration. This allows for names that are meaningful. When names aren't provided default to names by variable - same behaviour as today. ## Proposal Exact proposal details need to be determined. ## Additional details <!-- _NOTE: If the issue has addressed all of these questions, this separate section can be removed._ --> Some relevant technical details, if applicable, such as: - Does this need a gitlab~7884237? - Does there need to be an associated gitlab~15980522 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