Offboarding of [cuevas1876]

[jlang10761]

• name: Eric Cuevas
• team name: Clinical Decision Support(CDS)
• role on team: Engineer
• expected last day: 06/21/2024
• company they work for: Coforma
• email: eric.cuevas@coforma.io; eric.cuevas@va.gov
• GitHub username: _(Please include @ symbol): @cuevas1876
• COR: Keith Riley
• PM: Keith Riley
• additional access they may have: DSVA slack

:raised_hands: :tada: All done. Don't fill out or modify anything below here. :tada: :raised_hands:

Acceptance Criteria

Support Tier 1 🌺

The following steps are performed by the Platform Support Tier 1 team. Detailed instructions found here

• [ ] Requested removal from DSVA Slack (if applicable. Search for them in Slack)

  A comment on this ticket prefixed with /request (i.e. /request FirstName LastName) will send a message to the Slack admins automatically!

• [ ] Requested removal from Confluence (if applicable. Check confluence members)
• [ ] Remove from Platform Atlas (if applicable)
• [ ] User removed from the VA GitHub Org (if applicable. Check department-of-veterans-affairs/people)

  Fill out request found here.

• [ ] Pagerduty access removed (if applicable. Check pd users)
• [ ] Sentry access removed (if applicable. Check Sentry members)
• [ ] TestRail access removed (if applicable, Check TestRail User List)
• [ ] Zenhub license removed (If applicable. Check for license here)
• [ ] Okta account disabled

Support Tier 2 - DevOps 🌷

The following steps are performed by Platform Support Tier 2 DevOps. Detailed instructions found here

• [ ] SOCKS access removed (if applicable. Search their email in config.yml)

  Use the Remove SOCKS and AWS access Github Workflow. You'll need the user's email address associated with their public key (found in config.yml). Merge the PR.

• [ ] AWS access removed (if applicable. Search their name in AWS IAM)

  Use the same SOCKS and AWS access Workflow to remove user's entry from iam_users.tf. You'll need the user's AWS username (typically First.Last). Merge the PR and apply Terraform.

• [ ] Datadog (if applicable. Check Datadog users)
  • [ ] Disable in Datadog UI (must be done by a datadog admin)
  • [ ] Submit an ECC request (Only necessary if they were in the Datadog UI)
• [ ] Bot (va-bot, va-vfs-bot, and va-vsp-bot) user GitHub account(s) YubiKey(s) removed

  This is rare. See documentation for current users and removal process.

Other 🌻

• [x] Google analytics and Domo access removed (if applicable. Make sure the analytics-insights label is on this Issue)
• [x] Figma editor access removed (if applicable. Check Figma settings)

• [x] Removed from Monday Design Meeting invite

  CC: @department-of-veterans-affairs/vsp-operations , @department-of-veterans-affairs/platform-analytics-insights-team , @department-of-veterans-affairs/confluence-admins, @department-of-veterans-affairs/platform-design

[Blivaditis]

No GA No Domo

[stoiven]

https://github.com/department-of-veterans-affairs/va.gov-team/issues/86567

seems like a dupe issue

[rmtolmach]

Closing as duplicate like @stoiven mentioned.