Multiple systems -Tech Stack - Update Existing System

Tech Stack - Update Existing System

Context: as part of Reliability forming new subteams, we are defining new areas of system ownership and reflecting those changes in the tech stack. Note that in the provisioner fields I have added the user groups for the team owning the service. This group membership is updated when teams change, which will require fewer manual updates of adding/removing individual users in the tech stack moving forward.

Business/Technical System Owner or Delegate to Complete

Please do not merge before the Business Systems Analysts have reviewed and approved.

• Rename this MR's title to [System Name] - Tech Stack - Update Existing System

• Update data field(s) for the existing system within the 'Changes' tab of this MR. Commit update when ready. More instructions are here.

Are you changing the existing system's provisioner(s)?

• Yes. Create an Issue to add the new provisioner(s) of the system to the appropriate Google/Slack/GitLab groups:
  • correct team members are already assigned to the @gitlab-org/reliability/foundations and @gitlab-org/reliability/general groups, no issue required
• No

Are you removing an existing system from the Tech Stack?

• Yes. Be sure to complete a Tech Stack Offboarding Issue as well.
• No

Security Risk to Complete

Not required prior to merging

• Create Existing System - TS Update Tracking Issue in StORM board:
  • [Tracking Issue link]
• Once updates are finalized, sync changes with the ZenGRC System Object

/cc @gitlab-com/gl-security/security-assurance/security-risk-team