-
Notifications
You must be signed in to change notification settings - Fork 26
Sandbox Environment
This is a test/development environment, it's purpose is to give States interested in the eAPD system an opportunity to use and familiarize themselves with the system before diving into the Production site. Because this is a test/development environment no real data is allowed in the test/development site, and all data stored in the Sandbox environment will be periodically wiped out.
-
What is the eAPD Sandbox environment? The eAPD Sandbox environment is the eAPDs teams Staging environment. We use our Staging environment to test upcoming features and changes to the eAPD Application before they are released into Production. New features and changes are first tested in a Preview environment so the Sandbox/Staging environment should be mostly stable, but it is very much still a non-Production system.
-
How do I get access to the eAPD Sandbox environment? You need to create an account here, https://impl.reg.idm.cms.gov/registration.html?appid=eapd. Once you have the account, go to http://staging-eapd.cms.gov and log in. This will walk you through the process of requesting access to eAPD. However, the request still requires manual review and so is therefore, not instant access.
-
How often does the Sandbox environment get reset? The Sandbox environment receives updates multiple times a day, however this process incurs 0 downtime and should be seamless. This is however still a development environment, so there is a chance that an update will temporarily break the Sandbox environment. In most cases this will not require the data within the eAPD Sandbox environment to be reset. Our data reset cadence is once every 60 days or as needed development purposes, which is rare.
-
How do I get to the eAPD Sandbox environment?
https://staging-eapd.cms.gov
- Team Working Agreement
- Team composition
- Workflows and processes
- Testing and bug filing
- Accessing eAPD
- Active Documentation:
- Sandbox Environment
- Glossary of acronyms
- APDs 101
- Design iterations archive
- MMIS Budget calculations
- HITECH Budget calculations
- Beyond the APD: From Paper to Pixels
- UX principles
- User research process
- Visual styling
- Content guide
- User research findings
- eAPD pilot findings
- User needs
- Developer info
- Development environment
- Coding Standards
- Development deployment
- Infrastructure Architecture
- Code Architecture
- Tech 101
- Authentication
- APD Auto Saving Process
- Resetting an Environment
- Hardware Software List
- Deploying Staging Production Instances Using Scripts
- Terraform 101 for eAPD
- Provisioning Infrastructure with Terraform
- WebSocket basics
- Operations-and-Support-Index
- Single Branch Deployment Strategy
- Ops and Support Overview
- Service Level AOI
- Incident Response Plan
- On-Call Policy
- Infrastructure Contingency Plan
- Updating CloudFront Security Headers
- Requesting and Installing TLS Certificates