Vets-api terminal access for Tom Harrison

[tpharrison]

Your Name

Tom Harrison

Your GitHub handle (terminal access is managed through GitHub)

tpharrison

Your dsvagovcloud AWS user name (if applicable)

Tom.Harrison

Team, Role, and Company of the target individual

Authenticated Experience - Profile, BE Engineer, Adhoc

Product Manager (PM) name and email

Travis Cahill travis.cahill@agile6.com

Product Owner (PO) name and email

Samara Strauss samara.strauss@va.gov

COR Name (leave "None" if you listed an AWS user name above)

None

Vendor Onboarding Representative (VOR) Name (leave "None" if you listed an AWS user name above)

None

Please confirm if you are on the VFS Team Roster or Platform Team Roster

• VFS Team Roster
• Platform Team Roster

Please confirm E-QIP Transmittal/Adjudication. This could be a screenshot of your Transmittal/Adjudication email, a link to another request where you've submitted this proof (i.e. AWS/SOCKS), etc.

• I have attached proof that I have either transmitted my E-QIP survey or previously received a favorable decision (by including in "Additional Notes" section below)

ArgoCD terminal access requested for the following environments

• dev
• staging
• sandbox
• production (if requesting, justify prod access in 'Additional Notes' section)

Additional Notes

Here is a link to my AWS access approval - #42776

Additional resources for Support Engineer

• For users on a VFS team but not in the VFS Team Roster, they must start the Platform orientation process
• Instructions for handling requests here - Support Only

[bdech]

Confirmed in VFS Roster. E-QIP confirmed in linked AWS access request

[bdech]

The production justification for Tom's Vets-API production access request is directly related to this GitHub ticket.

[bdech]

@tpharrison Access to production is pending OCTODE approval.

[JonathanKamensDVA]

Approved. As usual, let's revisit in six months and remove the access if it is no longer needed or extend it otherwise.

[tpharrison]

Hi @JonathanKamensDVA. I just tried opening a ArgoCD console in production and I get the following...