CDCgov
Demo/Training: Update Device List to Match Production
Why should we do this?
- Current Experience: The list of devices available for selection on the Demo/Training site for SimpleReport does not accurately reflect the devices available in Production. This discrepancy creates confusion for new users who are familiarizing themselves with the application, and makes it difficult for the Customer Support team to effectively troubleshoot device issues.
- Why We Want to Make This Change: Customer Service should be able to confidently use the demo and training websites to troubleshoot issues customers are having with the same devices on production.
User story As a New User I want the list of devices available in Demo/Training to be identical to the list in Production so that I can learn the application efficiently and avoid errors when using it in my facility.
Action Requested Update the devices available on the demo.simplereport.gov and training.simplereport.gov websites to ensure they are identical to the devices available in the Production application.
Acceptance Criteria [ ] The devices available on the demo.simplereport.gov and training.simplereport.gov websites and reviewed and confirmed to match the devices available in Production. [ ] Functionality is tested to confirm all listed devices in Demo/Training can be selected and used as intended.
We've gotten the green light from @alismx / DevSecOps to expose device data in a public endpoint, which is how we want to drive the device seeding in demo / training. Should be able to work towards that goal now.
Tasks:
- [x] Add secrets to vault and terraform files (for storing token to make requests to prod for device data, etc...) [PR - #8323]
- [x] Add public devices endpoint protected by token that was added above [PR - #8341]
- [ ] Create endpoint and functionality to sync current env's
DeviceTypedata with prod's
Apologies that I never added this detail to the ticket itself. There is a concern based on some old conversations that removing the @JsonIgnore tag would potentially cause issues. We should make sure that we try to test this as best we can.