fail gracefully for S3 notifications and SNS delivery logs with strict service loading #9575
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
We would like users to have a smooth experience when disabling services:
logs
and still be able to publish (even if now it's opt-in and should be less of an issue)Changes
Add
is_api_enabled
checks before calling to return early.For example, a quick test with LocalStack started with
STRICT_SERVICE_LOADING=1
andSERVICES=s3
, setting up S3 notifications with an SQS queue destination:Calls are still successful and would be even without this PR as the notifications are asynchronous (except the verification of the target).
This is before this PR: