[Sign-in Service] - Application onboarding requirements checklist

[rileyanderson]

Description of application

Sign-in Service is an open source VA created OAuth solution which provides identity brokering for Login.gov, ID.me, DSLogon, and My HealtheVet credentials.

Sign-in Service currently lives inside vets-api and will be migrated out to this new application.

Because this is a migration of a core part of vets-api/va.gov, the plan is to get the infrastructure up for a barebones Rails app and then begin migrating the app over. Technical details and requirements may change as the migration proceeds.

Basic info:

Team Name:
Identity Surge

Application Name:
Sign-in Service

Functionality:
OAuth sign-in solution for vets-api

Language/Stack:
Ruby on Rails

Ports/Networking needed:
"80, 443" for standard HTTP and HTTPS - TBD

Other infrastructure needed:
RDS-Postgres 15.2, Elasticache- Redis 6.2

• https://github.com/department-of-veterans-affairs/devops/pull/12901

Background/Context/Resources

Sign-in Service currently lives inside vets-api and will be migrated out to this new application README

Technical Notes

• communication with vets-api (tbd)

---

Onboarding checklist

*The responsible parties are listed below each item in the checklist

Application repository and container

• [x] GitHub repo: https://github.com/department-of-veterans-affairs/sign-in-service Note: app should conform to the 12 factor app methodology | Docs
  Requesting team

• [x] Dockerfile: https://github.com/department-of-veterans-affairs/sign-in-service/blob/master/Dockerfile Requesting team

Application delivery pipeline (CI/CD)

• [ ] AWS service account for GitHub actions | Request here Infrastructure Team

  • svc-gha-identityteam-user Already exists. Need to add identity-sign-in-service ECR resource. https://github.com/department-of-veterans-affairs/devops/pull/12895

• [x] AWS Elastic Container Registry (ECR) repository for the app container: Submit PR to add your application name to the "all-repos" section of this page Requesting team

  • DONE - identity-sign-in-service https://github.com/department-of-veterans-affairs/devops/pull/12805

• [ ] Add semantic release configuration (a .releaserc file) to your repo | Example | Docs
  Requesting team

• [ ] Automation to push the app's container to ECR with a semantic version number | Example
  Note: Use sha or semver. Don't use default "latest" tag. The release system uses modified container image tags to synchronize automation.
  Requesting team

Application secrets and parameters

• [x] AWS SSM Parameter Store path created for your team or app, Infrastructure Team

  • /dsva-vagov/identity-team (Already exist)

• [ ] AWS SSM Parameter Store parameters that the app needs to run, ie /dsva-vagov/team-name/env/secret-name | Docs
  Requesting team

---

Once the checklist is complete, you will be ready to onboard your application. Visit Manage applications in EKS to get started.

Notes

• Please add comments to this issue as checklist items are completed, and...
• Tag the Infrastructure Team's product manager and product owner to help expedite the process

[va-vsp-bot]

This issue is stale. If it is no longer valid, please close issue. Otherwise please update

[kingbmike]

@rileyanderson Does this ticket/epic still have relevant work we need to complete?