-
Notifications
You must be signed in to change notification settings - Fork 64
Adding a Developer
Tim Best edited this page Sep 10, 2021
·
29 revisions
- Invite to application
- send new developer link: https://github.com/CDCgov/prime-simplereport/invitations
- after the developer accepts the invite. ask the developer to verify access to:
- Invite to static site
- send new developer link: https://github.com/CDCgov/SimpleReport_Public_Site/invitations
- Invite to internal docs
- send new developer link: https://github.com/usds/prime-simplereport-docs/invitations
- Invite to Coverity
- Invite to Snyk
-
Login to test.simplereport.gov and invite the new developer to your org as and admin of all facilities
-
After they sign up find their account in the Okta admin portal
-
Add them to the Prime Team Members group
-
add user to SimpleReport Engineering in the Okta preview account
- Add user to the
Prime Okta Adminsgroup in Okta - To make the user a site admin, add to admin group for each appropriate environment (
SR-${ENV}-ADMINS)
- set up the dev with a -su account process doc
- Ask dev to sign in to portal.azure.com
- Add the dev to the "SimpleReport Maintainers" group
- add developer to security alerts (https://github.com/CDCgov/prime-simplereport/settings/security_analysis)
- Add the dev to PagerDuty
- Prompt the dev to install the PagerDuty app and setup their notifications
- Add the user to the SimpleReport Escalation
- DAP: Ask dev to follow the instructions
- search.gov: add the user to https://search.usa.gov/sites/8523/users
- twilio
- sendgrid
🎉 🎉 🎉 🎉 🎉
- 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