Set OneTrust ID on GitLab.com

Epic: https://gitlab.com/groups/gitlab-org/-/epics/6347

Note: If doable, please schedule the config change within the first week of November (or sooner) due to the business requirements of rolling out the cookie banner. If that is not doable, please let me know and we can try to do a work-around in the code to not rely on the rollout.

Details

• Point of contact for this request: @nicolasdular

What is this issue about

With gitlab-org/gitlab!71243 (merged) we added OneTrust (Cookie Banner) to GitLab. The Banner requires an ID, which we introduced as a configuration in omnibus with gitlab-org/omnibus-gitlab!5655 (merged), called one_trust_id (within extra) and is added in GitLab Chart with gitlab-org/charts/gitlab!2237 (merged)

The cookie banner is behind a feature flag, setting the config has no immediate impact on production.

Request

Set one_trust_id to 7f944245-c5cd-4eed-a90e-dd955adfdd08 for gitlab.com.

Work

• Update helmchart in gstg 👉 gitlab-com/gl-infra/k8s-workloads/gitlab-com!1330 (merged)
• Set one_trust_id inside of of gstg 👉 gitlab-com/gl-infra/k8s-workloads/gitlab-com!1334 (merged)
• Update helmchart in gprd 👉 production#5847 (closed)
• Set one_trust_id inside of gprd 👉 gitlab-com/gl-infra/k8s-workloads/gitlab-com!1338 (merged)