Merges into master deploy to patchdemo-staging.catalyst.wmcloud.org
Closed, ResolvedPublic1 Estimated Story Points
Actions

Assigned To

Authored By

	SDunlap
	Sep 3 2024, 5:45 PM

Description

Staging needs to be in a managed, deployable state
Convert automatic deploy step for catalyst/patchdemo .gitlab-ci.yml to target staging
Convert automatic deploy step for Catalyst-API .gitlab-ci.yml to target staging
Add manual deployment step for Catalyst-API targetting production
Document deployment for both in their README

Mentioned Here: T373943: Staging deploys environments in a different namespace from production environments

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 3 2024, 5:45 PM

thcipriani updated the task description. (Show Details)

thcipriani set the point value for this task to 1.

thcipriani moved this task from Backlog to Ready on the Catalyst (AGL) board.

Add staging

Add staging

Edit environment names

Edit environment names

Fixup namespace

Fixup namespace

Each repo's CI is responsible for deploying its respective service in both staging and production.
Staging is automatically deployed on merges into master/main.
Deployment to production is a manual job which can be run after the pipeline finishes.
A new oauth client was created for patchdemo staging https://meta.wikimedia.org/wiki/Special:OAuthListConsumers/view/d73bc617e584344be9aefa5f2a641778
staging instances and deployed in a different namespace from production
staging instances have a separate databases from production instances
both staging and production Catalyst APIs deploy environments to the same namespace "cat-env" because this namespace is hardcoded
- created T373943 to fix

SDunlap closed this task as Resolved.Sep 6 2024, 7:03 PM