[lambda][output] updating slack output format to support large messages #135
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
ryandeivert
force-pushed
the
ryandeivert-make-slack-messages-pretty-again
branch
from
71ee325 to
b0ef4c4
Compare
ryandeivert
force-pushed
the
ryandeivert-make-slack-messages-pretty-again
branch
from
4eb7433 to
76b9cff
Compare
|
Fixed #135 |
ghost
mentioned this pull request
Closed
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.
to @airbnb/streamalert-maintainers
size: medium
changes
Slack output will now use attachments and split the message on the Slack recommended size of 4000 characters/bytes.
Output will also be formatted with tabs and "markdown" styling.
Messages will look similar to this in Slack (with the proper App name/icon):
Multi-part messages will have a
(Part # of n)string afterRecord