fix(e2e): improve e2e reliability for Gen1 branch#3435
Open
sarayev wants to merge 12 commits intorelease-api-plugin-stablefrom
Open
fix(e2e): improve e2e reliability for Gen1 branch#3435sarayev wants to merge 12 commits intorelease-api-plugin-stablefrom
sarayev wants to merge 12 commits intorelease-api-plugin-stablefrom
Conversation
…npm install - Increase sleep after SG rule addition from 1min to 5min in rds.ts (both after adding and after removing security group rules) - Add retry_with_backoff function definition to shared-scripts.sh (the call already existed but the function body was missing) - Wraps npm install -g @aws-amplify/cli-internal with retry_with_backoff 3
…s, add amplifyPushWithRetry - Add schema-iterative-update-1/2/3 to RUN_SOLO to prevent AppSync quota exhaustion - Fix searchable-node-to-node test: accept expectedCount param (was hardcoded to 1), handle null responses from 401 errors, increase retry window with capped backoff - Add amplifyPushWithRetry utility that retries on ApiLimitExceededException with exponential backoff (60s, 120s, 180s)
…O, regenerate YAML
…h-transformer Force-publish all packages that depend on graphql-elasticsearch-transformer to Verdaccio, not just the transformer itself. Previously, only the transformer was force-published (5.2.89), but its consumers (amplify-category-api, graphql-auth-transformer, graphql-transformers-e2e-tests) still had exact version pins to 5.2.88, which doesn't exist on Verdaccio and falls through to npm where the old t2.small.elasticsearch default exists (5.2.81). By force-publishing all dependents, lerna will: 1. Bump graphql-elasticsearch-transformer to a new version 2. Bump all its consumers to new versions 3. Update the exact dep specs in the published tarballs 4. Ensure the entire dependency chain resolves from Verdaccio
…st-install The npm-published @aws-amplify/cli-internal pins exact versions, so our local Verdaccio packages are bypassed for transitive deps like graphql-elasticsearch-transformer. Instead of force-publishing, we now patch the installed resources.js after npm install to replace deprecated t2.small/t2.medium.elasticsearch with t3 equivalents. Also reverts the --force-publish changes which were ineffective.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Ports applicable e2e reliability fixes from main branch to the Gen1 (release-api-plugin-stable) branch.
Changes
rds.ts: Increase SG propagation wait from 1min to 5min
setupRDSInstanceAndData(), wait 5 minutes instead of 1 minute for rules to propagateshared-scripts.sh: Add retry_with_backoff function definition
retry_with_backoff 3 npm install -g @aws-amplify/cli-internalis added but the function body was previously missingTesting
Related