[ENG-4000] fix(s3): remove bogus top-level data envelope from message format#642
Merged
Merged
Conversation
… format The S3 destination message format docs incorrectly wrapped read and subscribe action payloads in a top-level `data` object. The object body is the message payload itself, with no wrapper envelope. Fix the prose and both JSON examples. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
laurenzlong
approved these changes
Jun 30, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Fixes a mistake from #631. The S3 destination "Message format" section incorrectly documented read and subscribe action payloads as being wrapped in a top-level
dataobject. There is no wrapper envelope — the object body written to S3 is the message payload itself.Changes
action,projectId,result, etc. are at the top level.Both JSON examples were verified to parse. The JMESPath template
datanamespace (e.g.data.installationId) is unchanged — it's a handle to the payload root and remains correct.🤖 Generated with Claude Code