avoid client config generation race condition

[rtpascual]

Problem

There seems to be a race condition between client config generation and asserting post deployment, sometimes we see this error:

Compared to a successful run:

Issue number, if available:

Changes

Use existing waitForConfigUpdateAfterDeployment action to wait for amplify_outputs.json to be generated before interrupting sandbox and asserting post deployment.

Also following https://github.com/aws-amplify/amplify-backend/pull/2160, removed the rejectCleanupSandbox action since the prompt no longer exists.

Corresponding docs PR, if applicable:

Validation

E2E tests and canary test run https://github.com/aws-amplify/amplify-backend/actions/runs/11635102140.

Checklist

• [ ] If this PR includes a functional change to the runtime behavior of the code, I have added or updated automated test coverage for this change.
• [ ] If this PR requires a change to the Project Architecture README, I have included that update in this PR.
• [ ] If this PR requires a docs update, I have linked to that docs PR above.
• [ ] If this PR modifies E2E tests, makes changes to resource provisioning, or makes SDK calls, I have run the PR checks with the run-e2e label set.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[changeset-bot[bot]]

🦋 Changeset detected

Latest commit: 1ec2c610b679c8a867a95507d734982695928bd9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR