Automatically deploy staging when "Publish" is clicked

[daine]

📇 User story

As a content designer, I want to see the published content on the learning resources staging website as soon as I hit "Publish"

✅ Definition of Done

• [x] Webhooks setup in contentful
• [ ] Incoming webhooks setup in AWS Amplify for staging
• [ ] Webhooks in contentful is set to ACTIVE

📜 Acceptance criteria

• [ ] Clicking on "Publish" deploys content on the live staging sandbox
• [ ] Amplify webhooks written in terraform

🎨 More info

Here's how to setup incoming webhooks in AWS Amplify

I have tested this by doing click-ops and adding a webhook named contentful-publish:

TODO: Terraform that config^^^:

resource "aws_amplify_webhook" "main" {
  app_id      = aws_amplify_app.learning_resources.id
  branch_name = aws_amplify_branch.main.branch_name
  description = "contentful-publish"
}

---

I have created a contentful webhook for publishing. Here's what the current configuration looks like (it works!): .....and more configuration.....

How did I confirm that it works? I updated our "Contact Us" page and separated the sentences into a new paragraph (added a new line), and hit "Publish.

Webhook logs (triggered by hitting "Publish" on an entry):

Confirming that the webhook works on AWS Amplify:

AWS Amplify redeploying from the contentful webhook trigger

Screenshots of the website before, and after the changes:

Before deployment:

After deployment:

I have since reverted the change, and DEACTIVATED the contentful webhook

[anikbrazeau]

I wonder if this also might include a mechanism to control what's in staging and what's in production?

As a content designer, I want to see the content change on the learning resources staging website as soon as I hit "Publish" or " "Unpublish" in both English and French....and want to control when that content makes it to the production site.

I'm wondering if there might be a way to remove the automatic redeployment of Contentful content when a PR is merged? Would that help us control resource content more predictably?

[daine]

Putting this back on the backlog for clarity & refinement

[daine]

Grooming notes: This is currently deactivated so it is not working We need to know if this is something we need, could we re-activate it in staging? Hitting publish would be very similar to committing code, so does a redeployment make sense?