2024-02-08: Set arkose_labs_data_exchange_key application setting value

Production Change

Change Summary

Set arkose_labs_data_exchange_key application setting value to be used for ArkoseLabs Data Exchange feature implemented in gitlab-org/gitlab!139070 (merged) as part of https://gitlab.com/gitlab-org/modelops/anti-abuse/team-tasks/-/issues/529+.

Change Details

  1. Services Impacted - gitlab.com
  2. Change Technician - @ahanselka
  3. Change Reviewer - @ahanselka
  4. Time tracking - 5 minutes
  5. Downtime Component - None

Detailed steps for the change

Change Steps - steps to take to execute the change

Estimated Time to Complete (mins) - 1

  • Set label changein-progress /label ~change::in-progress
  • Copy value of arkose_labs_data_exchange_key in 1Password under ArkoseLabs API keys -> GITLAB - PRODUCTION - REGISTRATION FLOW - KEY 1
  • Run the following command in Rails console replacing <arkose_labs_data_exchange_key> with the value copied from 1Password 
    ::Gitlab::CurrentSettings.current_application_settings.update(arkose_labs_data_exchange_key: <arkose_labs_data_exchange_key>)
  • Set label changecomplete /label ~change::complete

Rollback

Rollback steps - steps to be taken in the event of a need to rollback this change

Estimated Time to Complete (mins) - 1

  • Run the following command in Rails console: 
    ::Gitlab::CurrentSettings.current_application_settings.update(arkose_labs_data_exchange_key: nil)
  • Set label changeaborted /label ~change::aborted

Monitoring

Key metrics to observe

  • Describe which dashboards and which specific metrics we should be monitoring related to this change using the format below.
  • Metric: Metric Name
    • Location: Dashboard URL
    • What changes to this metric should prompt a rollback: Describe Changes

Change Reviewer checklist

C4 C3 C2 C1:

  • Check if the following applies:
    • The scheduled day and time of execution of the change is appropriate.
    • The change plan is technically accurate.
    • The change plan includes estimated timing values based on previous testing.
    • The change plan includes a viable rollback plan.
    • The specified metrics/monitoring dashboards provide sufficient visibility for the change.

Change Technician checklist

  • Check if all items below are complete:
    • The change plan is technically accurate.
    • This Change Issue is linked to the appropriate Issue and/or Epic
    • Change has been tested in staging and results noted in a comment on this issue.
    • A dry-run has been conducted and results noted in a comment on this issue.
    • The change execution window respects the Production Change Lock periods.
    • For C1 and C2 change issues, the change event is added to the GitLab Production calendar.
    • For C1 and C2 change issues, the SRE on-call has been informed prior to change being rolled out. (In #production channel, mention @sre-oncall and this issue and await their acknowledgement.)
    • For C1 and C2 change issues, the SRE on-call provided approval with the eoc_approved label on the issue.
    • For C1 and C2 change issues, the Infrastructure Manager provided approval with the manager_approved label on the issue.
    • Release managers have been informed prior to any C1, C2, or blocks deployments change being rolled out. (In #production channel, mention @release-managers and this issue and await their acknowledgment.)
    • There are currently no active incidents that are severity1 or severity2
    • If the change involves doing maintenance on a database host, an appropriate silence targeting the host(s) should be added for the duration of the change.
Edited by Alex Hanselka