Eric Oliver Extended Leave Planning - CMS DevOps Engineer On-boarding

Background

I, Eric Oliver, will be starting (pending approval) extended leave. My leave will last 12 weeks starting August 10, 2023 and ends with my return November 2nd, 2023. This epic is meant to ensure:

A smooth transition of my responsibilities.
Existing DevOps team members have system(s) access and documentation to cover those responsibilities.
New DevOps team members have system(s) access and documentation to cover those responsibilities.

Generally, what current work needs to be handed off. Additionally, what specific CMS DevOps Engineer related on-boarding needs documenting and completing (e.g. AWS Access, Venafi Certificate Portal Access, CMS Server Access, etc.)

User Story or Problem Statement

As a CMS DevOps team member, I need to ensure my team has the proper tools, system access, and documentation that are used to complete my duties, so I can take extended leave without degrading or preventing the CMS DevOps team's ability to complete planned and unplanned work.

Affected users and stakeholders

CMS DevOps Team

Hypothesis

A hypothesis may depend on a spike ticket to be completed.

We believe that planning for extended leave will achieve an interrupted continuation of excellent service to CMS platform engineers and users. We'll know that to be true when planned or unplanned work is completed without undue difficulty.

Assumptions

Acceptance Criteria

[x] Eric's Existing tickets and responsibilities are documented.
[x] CMS DevOps Engineers tools, system access, and documentation to successfully complete work is documented.
[ ] CMS DevOps Engineers have the tools, system access, and documentation to successfully complete work.

Design principles

Runbook

## Labels (You can delete this section once it's complete) - [x] Issue type (red) (defaults to "Epic") - [ ] CMS subsystem (green) - [ ] CMS practice area (blue) - [x] CMS workstream (orange) - [ ] CMS-supported product (black) ### Team Please check the team(s) that will do this work. - [x] `CMS Team` - [ ] `Public Websites` - [ ] `Facilities` - [ ] `User support`

Rough list of what I can access and other DevOps engineers should have;

[x] Github CMS-bot login access via Security Key. Requires security key purchase. [Ticket Created] (https://github.com/department-of-veterans-affairs/va.gov-cms/issues/14345)
[x] Identity and Access Management PreProd Identity Provider membership. Allows Staging CMS PIV logon. Ticket Created
[ ] Service Now Change Management Group Membership.
[x] Venafi Certificate Management Portal. Access is controlled by ePAS. TIcket Created
[x] AWS Systems Manager access to CMS Servers. Ticket Created
[x] ~~General AWS access.~~
[x] cmsadmin distribution group membership and associated documentation. Distro group updated directly to include Tolase and Edmund Documentation
[x] PagerDuty account/membership Ticket Created
[x] Github Team membership Added @teeshe to cms-infrastructure
[x] OKTA Access for Datadog Ticket Created

Striking "General AWS Access" since Nate, Edmund and Tolase have Administrator access to the DSVA Govcloud account.

I'm going to leave the change management related on-boarding for later. It's not critical right now, and hopefully becomes unnecessary in the future.

11/2/2023 Edit: Should this team use this in the future also include Packagist membership as an item.

department-of-veterans-affairs / va.gov-cms