-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
add empty integrations for NG APIGW #11099
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 22m 56s ⏱️ - 1h 12m 5s Results for commit 7a5b2c3. ± Comparison against base commit 79a10dc. This pull request removes 2508 tests.
♻️ This comment has been updated with latest results. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀 LGTM!
) | ||
|
||
integration_response = integration.invoke(context) | ||
response.update_from(integration_response) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, that is keeping things nice and simple! 🚀
Motivation
This is first iteration to introduce the different REST API integrations.
The first idea was to use Plugins for each different
IntegrationType
, which allows easy discovery and to extend the list of integration in a transparent way.However, while working on the
AWS
integration type, it became apparent that we could pull off all AWS services with a single integration, with no need to subclass like the current code does (we haveKinesisIntegration
,S3Integration
...). But it happens that theAWS
integration has the same logic for every service, and we will work to make it possible in the new iteration.Changes