-
Notifications
You must be signed in to change notification settings - Fork 53
Adding a Developer
elisa lee edited this page Mar 28, 2024
·
28 revisions
This set of instructions is for tech leads or others on the project who need to add a new developer to the team.
- Invite to the main repository (this one!)
- After the dev accepts the invitation, ask them to verify access to:
- Invite to the static site repo
- Invite to internal docs repo
- You'll need to invite them as an "outside collaborator" at first - more details are in the docs wiki.
- Invite to Coverity
- Invite to Snyk
You need to make sure they've been invited to both Prod and Preview Okta.
- Login to test.simplereport.gov and invite the new developer to your org as an admin of all facilities
- Find their account in the Okta admin portal
- Add to the following groups:
- Prime Team Members
- SimpleReport Engineering
- SR-PENTEST-ADMINS
- SR-TEST-ADMINS
- SR-DEV-ADMINS
- SR-DEV2-ADMINS (and any other development environments they'll need)
- Add to all the SimpleReport applications (especially
SimpleReport (local dev)
) - Make sure they're a member of at least one organization in each environment (it's usually sufficient to add to ADMINS and NO_ACCESS for a given org - admins lets them see the full app view, and no_access ensures they're linked to the SimpleReport database)
- Directly add the user through the Okta admin portal.
- Add to the following groups:
SR-PROD-ADMINS
Prime Team Members
-
Prime Okta Admins
(only add if the developer will be in the on-call rotation) SR-STG-ADMINS
SR-STG-TENANT:6eaeeb05-e3ab-48e0-a793-b19d71e2302a:NO-ACCESS
SR-STG-TENANT:6eaeeb05-e3ab-48e0-a793-b19d71e2302a:ADMIN
- Invite to production Metabase
- Invite to test Metabase (you may need to ask the DevOps team for assistance, depending on the environment)
Follow the email instructions in the docs wiki to give Azure access.
- Request that the user be added to the CDCgov Github organization (this is required to put them on review teams.) You can request access with this board.
- Once the user's been added to CDCgov, add them to the appropriate review teams.
- For CDCent, the user no longer needs to be an outside collaborator and can be a full member. Follow the instructions linked in the docs wiki.
- Add developer to security alerts, if appropriate
- Add the dev to PagerDuty
- Prompt the dev to install the PagerDuty app and setup their notifications
- Once the developer is familiar with Azure and has completed a shadow rotation, add them to the SimpleReport rotation
- DAP: Ask dev to follow the instructions
- search.gov: add the user to https://search.usa.gov/sites/8523/users
- Twilio
- Sendgrid
- Touchpoints
Welcome to the team! 🎉 🎉 🎉 🎉 🎉
- Getting Started
- [Setup] Docker and docker compose development
- [Setup] IntelliJ run configurations
- [Setup] Running DB outside of Docker (optional)
- [Setup] Running nginx locally (optional)
- [Setup] Running outside of docker
- Accessing and testing weird parts of the app on local dev
- Accessing patient experience in local dev
- API Testing with Insomnia
- Cypress
- How to run e2e locally for development
- E2E tests
- Database maintenance
- MailHog
- Running tests
- SendGrid
- Setting up okta
- Sonar
- Storybook and Chromatic
- Twilio
- User roles
- Wiremock
- CSV Uploader
- Log local DB queries
- Code review and PR conventions
- SimpleReport Style Guide
- How to Review and Test Pull Requests for Dependabot
- How to Review and Test Pull Requests with Terraform Changes
- SimpleReport Deployment Process
- Adding a Developer
- Removing a developer
- Non-deterministic test tracker
- Alert Response - When You Know What is Wrong
- What to Do When You Have No Idea What is Wrong
- Main Branch Status
- Maintenance Mode
- Swapping Slots
- Monitoring
- Container Debugging
- Debugging the ReportStream Uploader
- Renew Azure Service Principal Credentials
- Releasing Changelog Locks
- Muting Alerts
- Architectural Decision Records
- Backend Stack Overview
- Frontend Overview
- Cloud Architecture
- Cloud Environments
- Database ERD
- External IDs
- GraphQL Flow
- Hibernate Lazy fetching and nested models
- Identity Verification (Experian)
- Spring Profile Management
- SR Result bulk uploader device validation logic
- Test Metadata and how we store it
- TestOrder vs TestEvent
- ReportStream Integration
- Feature Flag Setup
- FHIR Resources
- FHIR Conversions
- Okta E2E Integration
- Deploy Application Action
- Slack notifications for support escalations
- Creating a New Environment Within a Resource Group
- How to Add and Use Environment Variables in Azure
- Web Application Firewall (WAF) Troubleshooting and Maintenance
- How to Review and Test Pull Requests with Terraform Changes