Unsave Feast Recipes from Feast Web Nudges

[andresilva-guardian]

What does this change?

Adds an unsave action for Feast recipes saved from web articles.

• Adds a DELETE saved-from-web client request with bearer authentication.
• Retries Feast API 503 responses with exponential backoff.
• Clears cached saved-recipe state after successful save or unsave mutations.
• Adds a Braze banner UNSAVE_FEAST_RECIPE_BY_ID message handler and unsave analytics event.

Why?

Readers need to be able to remove recipes they have previously saved from an article, using the same Feast banner integration that supports saving.

How has this change been tested?

Automated tests

• savedFromWeb.test.ts
  • Successful DELETE request with correct auth headers.
  • Idempotent 204 No Content response.
  • Retry after a 503 response.
  • Saved-status cache invalidation after removal.
• BrazeBannersSystem.test.tsx

Both focused suites pass: 26 tests.

Manual testing

Not performed.

Screenshots

No visual changes.

[github-actions]

Hello 👋! When you're ready to run Chromatic, please apply the run_chromatic label to this PR.

You will need to reapply the label each time you want to run Chromatic.

Click here to see the Chromatic project.

[github-actions]

🚀 Image pushed to AWS ECR

Image digest: sha256:09f73a532609fad809f5d400a2b4aa39d47201f45f677dd82cc3d43a51813cb4

🐛 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:09f73a532609fad809f5d400a2b4aa39d47201f45f677dd82cc3d43a51813cb4"

# Refer to image using branch tag
# IMAGE_IDENTIFIER=":branch-afs-unsave-feast-recipe-from-the-web"

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

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

# 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 30577 of dotcom:rendering-all to CODE

All deployment options

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

---

From guardian/actions-riff-raff.