Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare AG environment for m4/m5 UAT #3112

Open
3 tasks
katypies opened this issue Nov 22, 2024 · 1 comment
Open
3 tasks

Prepare AG environment for m4/m5 UAT #3112

katypies opened this issue Nov 22, 2024 · 1 comment
Labels
dev issue is for the dev team Feature: 🏢 Org Model

Comments

@katypies
Copy link
Contributor

katypies commented Nov 22, 2024

Issue description

We're closing in on completion of m4/m5! UAT will be conducted in AG. We need to prepare the environment in preparation for UAT.

Product plans to conduct UAT in Sprint 61.

Acceptance criteria

  • Copy all data from staging onto AG
  • reserve AG for UAT effort
  • deploy latest Staging release to AG for UAT upon product request (use the last staging release tag)

Additional context

I'm assuming we'll use AG again. This can be updated for a different sandbox, too, if that's preferred for this UAT.

Note for copying data from Staging to Ag you should be able to follow what was done to clone staging to MS, this is the last PR were the deploy-staging workflow was targeting ms (not in this case you just want to target ag), you also should just do these commands by hand instead of trying to make a new workflow.

Links to other issues.

For further reference, this PR is the one when our workflow was switched to pull stable in staging. Please don't try to copy directly from stable, to avoid any accidents.

@abroddrick
Copy link
Contributor

Added an AC for just pulling the most recent updates from staging to the chosen sandbox. I'm fine with ag, though we could use any sandbox (besides development and staging).

@abroddrick abroddrick moved this from 👶 New to 🎯 Ready in .gov Product Board Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev issue is for the dev team Feature: 🏢 Org Model
Projects
Status: 🎯 Ready
Development

No branches or pull requests

2 participants