feat: Addition of Amazon S3 Event Notifications #245
+385
−4
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
added 4 commits
January 2, 2025 17:42
|
Hey @bryantbiggs ! Happy new year 2025 ! with all my best wishes of success ! |
bryantbiggs
reviewed
Jan 6, 2025
bryantbiggs
reviewed
Jan 6, 2025
bryantbiggs
reviewed
Jan 6, 2025
bryantbiggs
reviewed
Jan 6, 2025
bryantbiggs
reviewed
Jan 6, 2025
schniber
changed the title
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.
Description
This PR aims at fixing #244 and adds the support of Amazon S3 Event Notifications through the Slack Lambda function.
Motivation and Context
This PR aims at fixing #244
Breaking Changes
No Breaking Changes
How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request