Repository navigation
Make strict adherence to AWS SQS purge queue behaviour optional - #10409
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #10409 +/- ##
=======================================
Coverage 93.47% 93.47%
=======================================
Files 1346 1346
Lines 123451 123454 +3
=======================================
+ Hits 115396 115401 +5
+ Misses 8055 8053 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
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.
resolves #10404
Related Issue #10233
Related PR #10234
One use-case for Moto and Moto server is in tests to mock AWS endpoints. Sometimes that means strict adherence to AWS is undesirable, IMO a limit of one SQS purge queue request every 60 seconds is such a scenario. This PR allows for users to optionally disable this behaviour by setting an environment property
MOTO_SQS_ENFORCE_STRICT_QUEUE_PURGE_BEHAVIOURto false