Assign new AB tests to MVT ids randomly

[Jakeii]

What does this change?

Why?

How has this change been tested?

Screenshots

Before	After

[github-actions]

🚀 Image pushed to AWS ECR

Image digest: sha256:3703dcf800b5946804f90118fb3eed6d458ac1c0abe8b3e892a23239ab2109b1

🐛 Run the image locally

The following can be used to run the image locally:

# Refer to image using the immutable digest. Find alternatives below.
IMAGE_IDENTIFIER="@sha256:3703dcf800b5946804f90118fb3eed6d458ac1c0abe8b3e892a23239ab2109b1"

# Refer to image using branch tag
# IMAGE_IDENTIFIER=":branch-ab-test-random-assignment"

# Refer to image using build tag
# IMAGE_IDENTIFIER=":build-30462"

# Refer to image via the GitHub commit SHA tag
# IMAGE_IDENTIFIER=":sha-9c34adeb2382ffdc18d1919c46f9e4c9587c3a8e"

# Set environment variables for the AWS CLI
AWS_PROFILE="<A_PROFILE_FROM_JANUS>"
AWS_DEFAULT_REGION="eu-west-1"

IMAGE_ACCOUNT_ID=$(aws ssm get-parameter --name /organisation/accounts/deployTools --query "Parameter.Value" --output text)
REGISTRY="${IMAGE_ACCOUNT_ID}.dkr.ecr.${AWS_DEFAULT_REGION}.amazonaws.com"
IMAGE="${REGISTRY}/guardian/dotcom-rendering${IMAGE_IDENTIFIER}"

# Login to AWS ECR https://docs.aws.amazon.com/AmazonECR/latest/userguide/registry_auth.html
aws ecr get-login-password | docker login --username AWS --password-stdin $REGISTRY

# Pull the image
docker pull $IMAGE

# Run the image. You'll likely need to set additional flags. See https://docs.docker.com/reference/cli/docker/container/run.
docker run $IMAGE

---

From guardian/actions-publish-image.

[github-actions]

Deploy build 30462 of dotcom:rendering-all to CODE

All deployment options

• Deploy build 30462 of dotcom:rendering-all to CODE
• Deploy parts of build 30462 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.