Skip to content

chore: place the constant in a common area

Manoj M Jrequested to merge
mmj-refactor-header into main

What does this merge request do and why?

Refactor towards: gitlab-org/gitlab#566553 (closed)

We move the constant to a common area in lib so that it can be imported from there in duo workflow service too, rather than importing from AI Gateway related files.

This change consolidates the definition of a header name used for enabling verbose AI logging. Previously, the header name "x-gitlab-enabled-instance-verbose-ai-logs" was defined locally in one file, but now it's been moved to a central location in the verbose AI logs library and given a clear constant name. All the code that was using the old local definition has been updated to use this new centralized constant instead. This makes the code more maintainable by having the header name defined in one place rather than duplicated across multiple files, and makes it easier to change the header name in the future if needed.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Merge request checklist

  • Tests added for new functionality. If not, please raise an issue to follow up.
  • Documentation added/updated, if needed.
  • If this change requires executor implementation: verified that issues/MRs exist for both Go executor and Node executor or confirmed that changes are backward-compatible and don't break existing executor functionality.

Merge request reports