Skip to content

4.3 — Configure staging environment #58

@davidortinau

Description

@davidortinau

Description

Set up a separate Azure staging environment for pre-production testing. Staging uses same architecture as production but reduced SKUs for cost savings, seed test data.

Dependencies

Acceptance Criteria

  • azd env new staging creates separate resource group
  • Staging database, Redis, storage provisioned separately
  • Reduced SKUs: PostgreSQL Basic, Redis Basic C0 (vs Standard in prod)
  • Staging Entra ID app registration configured with staging redirect URIs
  • Test data seeded (user accounts, vocabulary, activities)
  • Staging deployment pipeline working (auto-deploys on main push)
  • Staging environment stable and accessible

Technical Notes

  • Aspire generates separate resources per environment
  • Cost per month: staging << production
  • Use staging to test deployments before production

Phase: 4 | Size: M | Owner: Zoe (Lead)

Metadata

Metadata

Assignees

No one assigned

    Labels

    phase:4-pipelinePhase 4: Deployment Pipelinesize:MMedium task (3-5 days)squadSquad triage inbox — Lead will assign to a membersquad:zoeAssigned to Zoe (Tester)

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions