This repository was archived by the owner on Mar 23, 2026. It is now read-only.
refactor sqs deveoper api into its own module#13202
Merged
Conversation
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 2h 6m 13s ⏱️ Results for commit 3f62692. |
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 1h 35m 40s ⏱️ - 24m 7s Results for commit 3f62692. ± Comparison against base commit 1d26fe7. This pull request removes 995 and adds 47 tests. Note that renamed tests count towards both. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Motivation
There were two long-standing issues in our internal issue tracker to:
provider.pyfor better readability and maintainabilityThis PR achieves those two things.
The PR looks like a lot of changes, but really all I did was
SqsDeveloperEndpointsfromprovider.pyintodeveloper_api.py(I also renamed it toSqsDeveloperApi, which I think is more fitting)provider.pyintoutils.pyormodels.py- otherwise we'd have a circular referencecreate_message_attribute_hashthat moved intoutils.pyThis also triggered a minor import change in lambda, which uses SQS internals.
Changes