Skip to content

Send GitLab version and hostname during instance activation

What does this MR do and why?

Part of Include more info about the SM instance during ... (#433276 - closed)

This depends on https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/8944+ to be merged first

Prior to this change, only the activation code, instance identifier and if the activation is automated was sent during the instance activation. For upcoming new feature, the GitLab version will be needed to be synced during the activation.

This change sends info about the instance's GitLab version and its hostname during the instance's activation to allow the data to be present from the get go and allow future features.

Due to the performance concerns, only the GitLab version and the hostname are added here and users count (billable and max) will continue to only be synced with the seat link sync.

How to set up and validate locally

  1. Buy a new subscription or use an activation code of a subscription that you haven't used for an activation yet.
  2. Use the subscription's activation code to activate it on your GDK.
  3. Verify the activation was successful.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Corinna Gogolok

Merge request reports