Planning issue for CustomersDot portal for Staging Ref
Follow-up on #338974 (closed)
Staging Ref should have pre-created users with Admin/Owner access on different plans (starter,premium) (more details in https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/576).
This issue is to plan the work that is required to achieve the above.
Steps
- Set up CustomersDot portal for Staging Ref - this will be a new standalone CustomersDot portal in GCP per #342150 (comment 699980303)
- Connect CustomersDot instance to Staging Ref
- Explore if this can be automated: if Staging Ref is destroyed and rebuilt - everything should be set up during rebuilding.
- Create test users with various paid tiers (related to https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/576 and #339992 (comment 673478617))
Staging Ref
Infrastructure and Quality teams are working currently on adding a new staging environment called Staging Ref where engineers will have full access to Gitlab environment and will be able to test their features without restrictions that they have on the current Staging.
Staging Ref will be 10k hybrid environment (GCP) and can be destroyed/rebuilt if needed. Please see &6401
-> staging-ref (new) -> QA
/
gstg-migrations -> gstg-cny (new) -> QA (new) -> gstg -> QA -> gprd-migrations -> gprd-cny -> QA -> gprd
Staging Ref is deployed with GitLab Environment Toolkit and will be wired in to the main Deployer pipeline in https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/14046.
If Staging Ref is rebuilt, after it should be seeded with all required test data. Here's the table overview for test data requirements - #338976 (comment 692771563)
cc @chloeliu