2022-03-15: Delete marketo hook

Production Change

Change Summary

See gitlab-org/gitlab#340426 (closed)

This change is to manually delete the now defunct Marketo hook (WebHook.find(67407)).

Change Details

  1. Services Impacted - ServiceUnknown
  2. Change Technician - @ahmadsherif
  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) - Estimated Time to Complete in Minutes

  • Login with RW access to a production console
  • Find the hook: webhook = WebHook.find(67407)
  • Verify that the webhook is correct:
    • It should be invalid: webhook.invalid?
    • It should have webhook.type == 'ProjectHook'
    • It should have webhook.url =~ /marketo/
  • Destroy the hook: webhook.destroy!

Rollback

There are no rollback steps.

Monitoring

Key metrics to observe

Nothing needs monitoring. This hook is defunct.

Summary of infrastructure changes

  • Does this change introduce new compute instances? NO
  • Does this change re-size any existing compute instances? NO
  • Does this change introduce any additional usage of tooling like Elastic Search, CDNs, Cloudflare, etc? NO

Change Reviewer checklist

C4 C3 C2 C1:

  • 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.

C2 C1:

  • The complexity of the plan is appropriate for the corresponding risk of the change. (i.e. the plan contains clear details).
  • The change plan includes success measures for all steps/milestones during the execution.
  • The change adequately minimizes risk within the environment/service.
  • The performance implications of executing the change are well-understood and documented.
  • The specified metrics/monitoring dashboards provide sufficient visibility for the change. - If not, is it possible (or necessary) to make changes to observability platforms for added visibility?
  • The change has a primary and secondary SRE with knowledge of the details available during the change window.

Change Technician checklist

  • This issue has a criticality label (e.g. C1, C2, C3, C4) and a change-type label (e.g. changeunscheduled, changescheduled) based on the Change Management Criticalities.
  • This issue has the change technician as the assignee.
  • Pre-Change, Change, Post-Change, and Rollback steps and have been filled out and reviewed.
  • This Change Issue is linked to the appropriate Issue and/or Epic
  • Necessary approvals have been completed based on the Change Management Workflow.
    • for C4, no specific approval is needed.
  • [-] Change has been tested in staging and results noted in a comment on this issue.
    • NA
  • A dry-run has been conducted and results noted in a comment on this issue.
    • NA: deleting a record is too simple for a dry-run.
  • 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.)
  • [-] Release managers have been informed (If needed! Cases include DB change) prior to change being rolled out. (In #production channel, mention @release-managers and this issue and await their acknowledgment.)
    • NA
  • There are currently no active incidents.
Edited by Ahmad Sherif