cagov / ui-claim-tracker

This repo contains the Claim Status Tracker app, which helps Californians better understand what’s happening with their unemployment claim and benefits.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Request and configure new environments

kalvinwang opened this issue · comments

Description

This ticket should cover requesting new environments from CDT and BAS, configuring environments to complete the setup, and testing that the environments work as desired.

Acceptance Criteria

  • 1. Verify Front Door route matching approach: We are not currently able to support multiple context roots. We believe that we have identified a potential solution by moving the route handling out of the application and into Front Door, but we need to confirm.
    • Status: We're currently working with CDT to configure Front Door
    • /claimstatus loads correctly
    • /claimstatus?from=uiom loads correctly
    • /claimstatus/es loads correctly
    • Static assets load correctly
    • Deploy proof of concept to TEST and verify it works correctly when someone within EDD network authenticates and clicks the CST icon
      • Deployed
      • EDD confirmed
  • 2. We request the number of environments needed from CDT: Depending on the outcome of the Front Door route matching test above, we will request either 2 or 3 additional environments. We need to specify details for each of the following:
    • App Service development slots
    • Application Insights
    • Front Door
    • Custom Domain
    • Azure Devops
  • 3. CDT configures new environments: Once CDT receives the requirements from us, they configure the new environments.
    • Requested
  • 4. We confirm DNS requirements with CDT: Once we determine the number of environments, we confirm the correct DNS updates with CDT.
  • 5. BAS configures DNS: Once we confirm the correct DNS with CDT, BAS makes the necessary changes.
    • Requested
  • 6. Once DNS is configured, CDT sets up the Front Door for each environment
    • Requested
  • 7. CDT configures WAF policies: Once we determine what WAF policies we'd like to request, CDT configures them.
    • Requested
  • 8. We complete configuration for new environments: Once CDT configures the environments, we configure the Application Settings for each environment and deploy the correct branch to each environment
  • 9. We test new environments: We verify that CST is working correctly in each of the environments and deploys to each environment works.

Note for future work: don't forget to include WAF policies as part of the initial request to CDT.

I've completed our portion of the configuration and testing for the new environments. Remaining outstanding items:

  • Custom Domain vs Front Door
  • WAF policy custom policies by IP group

CDT has completed their work and confirmed the DNS changes. Moving this to "In review" because the last items are for EDD to verify the environments.

Note for future work: don't forget the step to ask IDM team to update the environment endpoints.

Note for future work: don't forget the step to ask UIO team to update the global header links in each environment.

Testing completed today. UIO successfully tested access to all 3 new environments.