Bypass staging rate limiting when running cypress tests #2046
Conversation
This file contains 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
🧪 Review environmenthttps://5fc4iv7zd6uvud3awewucfixzu0ugnhp.lambda-url.ca-central-1.on.aws/ |
…tatements to print part of the key to ensure its actually there and correct
andrewleith
changed the title
andrewleith
deleted the
fix/bypass-rate-limit-for-static-files-cypress
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 | Résumé
This PR updates the cypress test suite to pass a
waf-secretheader on every request to notify (including static resources) in order to bypass rate limiting.Test instructions | Instructions pour tester la modification