Closed olivereri closed 12 months ago
Rough list of what I can access and other DevOps engineers should have;
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.
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:
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
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
Design principles
Runbook