aws-amplify / aws-amplify/amplify-hosting

Add verify build settings to Amplify Console

Open
#2,773 2 comments 2 reactions 0 assignees View on GitHub
feature-request
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

### Is this related to a new or existing framework?

_No response_

### Is this related to a new or existing API?

New API

### Is this related to another service?

_No response_

### Describe the feature you'd like to request

We'd like to run e2e test after deployment of Amplify Console. Amplify's `test` phase is before deployment and the e2e test you have as an example is not real e2e. https://aws.amazon.com/blogs/mobile/run-end-to-end-cypress-tests-for-your-fullstack-ci-cd-deployment-with-amplify-console/

If we could specify something similar to `test` build settings as `verify` stage, we could run our e2e test against the production/staging/preview endpoints automatically after deployment and verify the deployment was healthy or not. However, I couldn't find such configuration here: https://docs.aws.amazon.com/amplify/latest/userguide/build-settings.html

### Describe the solution you'd like

As I mentioned above, adding the build settings for `verify` stage. Then, Amplify Console will run the preVerify, verify and postVerify phases after deployment automatically.

### Describe alternatives you've considered

Amplify Console only has email notifications. So, we could build Amazon SES receiver and do some job there. But it's not trivial and also we need some infrastructure to run the e2e test unlike `test`.

### Additional context

The e2e test itself might be running outside the build environment and the spec can be just kick the other service and wait for it.

### Is this something that you'd be interested in working on?

- [ ] 👋 I may be able to implement this feature request
- [ ] ⚠️ This feature might incur a breaking change

Contributor guide

Open the contributing guide

Research direction

Start with the Amplify Console build-settings documentation and the linked Cypress deployment example, then compare them with the existing test phase described in the issue. The issue names no repository files or tests; completion would require a defined verify-stage configuration that runs after deployment and reports whether the deployed endpoint passes verification.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
ci-cd, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.