Description
Status
Date | Status | Launch Date | Notes |
---|---|---|---|
2025-3-7 | In Progress | Behind Schedule (MS3 - Q2 2025) | We have completed the blocking portion of the param store normalization effort, the remaining cleanup will be conducted under Milestone 4. We are beginning on helm chart and docker image work for vets-api. Param store reviews have taken longer than anticipated and have delayed overall Milestone 3 progress. With that work completed, we're increasing staffing on this effort to accelerate the completion of Milestone 3. |
2025-2-24 | In Progress | On Track (MS3 - Q1 2025) | Completed alignment on approach changes to param store updates, finishing updates to UI/UX designs. Conducted technical deep dive with the team. |
2025-2-10 | In Progress | On Track (MS3 - Q1 2025) | Work ramped down this sprint due to key staff on T2 support rotation, will resume as planned next sprint. Had a meeting to discuss Identity team's concern with the implication of Param Store/Helm Chart normalization work. |
2025-1-24 | In Progress | On Track (MS3 - Q1 2025) | We are finishing up work on parameter store normalization, this sprint or next sprint. |
2025-1-13 | In Progress | On Track (MS3 - Q1 2025) | Milestone 3 is progressing. good progress made over the holiday sprints, continued work on helm charts. |
2024-12-18 | In Progress | On Track (MS3 - Q1 2025) | Milestone 3 is progressing. Helm chart normalization was moving forward more smoothly during the span of this sprint. |
2024-12-5 | In Progress | On Track (MS3 - Q1 2025) | Milestone 3 is progressing. The helm chart normalization work is progressing slower than anticipated due to the thoroughness of the reviews on the work. We'll bring other Milestone 3 work forward to fill the gaps. |
2024-11-22 | In Progress | On Track (MS3 - Q1 2025) | Milestone 3 in progress, initial param store normalization has been completed, and is waiting for helm chart normalization work to complete before it can be resolved. Helm chart normalization is beginning in sprint 15. |
2024-11-7 | In Progress | On Track (MS3 - Q1 2025) | Milestone 3 is progressing, param store normalization almost complete, should complete next sprint, no blockers |
2024-10-23 | In Progress | On Track (MS3 - Q1 2025) | Milestone 3 is progressing, param store normalization should complete next sprint, no blockers |
2024-10-09 | In Progress | On Track (MS3 - Q1 2025) | Param store normalization in progress |
Product Outline
Preview Environments Product Outline
High Level User Story/ies
As a developer on the VA.gov platform, I need robust and flexible preview environments so I can efficiently test changes in a simulated production-like setting without impacting the live environment.
Hypothesis or Bet
If _we enhance preview environments with additional features like standardized helm charts, parameter store normalization and override, authentication/use of mock and staging test data, and additional feature then we expect developers will be able to use preview environments effectively as a replacement for Review Instances, and Review Instances can begin to be sunset.
Complete Feature List for Milestone 3
OKR
2023-Objective 2 - Enhance Platform technologies and processes to be agile and scalable to tolerate at least a 50% unexpected increase in VFS product development workloads and Veteran end-user usage. (Was not associated w/ a specific KR)
(This applies to the Preview Environment effort overall)
Definition of Done
- Preview Environments vets-website, vets-api, content-build versions can be customized to fit the user/team's need
- Users can select between mock data or staging test data for their preview environment when created outside of a Pull Request.
- Environments automatically expire, with manual destruction available
- A unified Helm chart is used for both Production and Preview environments.
- Non-release containers and helm charts are cleared from ECR monthly.
- Configuration defaults to Staging parameter store values unless overridden during creation.
Success Metrics
- Number of Preview Environments created and utilized is greater than 5%
- Decline in negative comments about testing environments
Projected Launch Date
We expect to complete this epic by Q1 2025.
Activity