Add Amazon S3 publishing integration docs page#1707
Conversation
Document the new Amazon S3 publishing integration: configuration fields, object layout (timestamped snapshot + rolling latest.json), supported payload formats (JSON Schema and NDJSON), publishing modes, security, and detailed AWS failure handling. - New page pages/publishing/publishing/amazon-s3.mdx - List all publishing integrations alphabetically in _meta.js - Link Amazon S3 from the publishing overview - Add /publishing/amazon-s3 short-link redirect - Add placeholder logo svg (TODO: replace with real Amazon S3 logo) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughThis PR introduces documentation for Amazon S3 as a publishing destination within Avo's documentation site. The changes include routing configuration, sidebar navigation metadata, a new comprehensive documentation page covering AWS setup and Avo integration, and links from the overview page. ChangesAmazon S3 Publishing Documentation
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@pages/publishing/publishing/amazon-s3.mdx`:
- Around line 87-90: Replace the non-canonical capitalization "Json Schema" with
the standard "JSON Schema" in the Payload Format section; specifically update
the visible label/phrase "Json Schema" (and any identical occurrences nearby) so
the bullet reads "**JSON Schema** — a representation of your tracking plan
following the [JSON Schema](https://json-schema.org/) standard." to maintain
consistent naming.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: b75d4709-2014-4b27-b83f-0cd5f890687c
⛔ Files ignored due to path filters (1)
public/images/publishing_amazon_s3.svgis excluded by!**/*.svg
📒 Files selected for processing (4)
next.config.mjspages/publishing/publishing/_meta.jspages/publishing/publishing/amazon-s3.mdxpages/publishing/publishing/overview.mdx
Replace the grey placeholder with the S3 bucket glyph from the app (IconS3Integration.res), converted to a static SVG with a fixed gradient id. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Match the renamed field in the Avo app. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Address CodeRabbit review on PR #1707. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Document the OIDC-federation Role Assumption mode alongside the existing Access Keys mode: trust policy (Federated accounts.google.com + sts:AssumeRoleWithWebIdentity + aud condition), GCP-service-account audience the customer pastes, per-publish JWT exchange flow, security framing, config table rows, and OIDC-specific failure entries. Access Keys mode unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@pages/publishing/publishing/amazon-s3.mdx`:
- Around line 58-74: Update the OIDC trust policy JSON: keep "Principal": {
"Federated": "accounts.google.com" } intact, but change the Condition so
"accounts.google.com:aud" matches the Google ID token audience/client ID (not
the GCP service account email); if you need to restrict to a specific service
account, add a separate claim restriction using "accounts.google.com:sub" with
the service account's subject value rather than using the service account email
for "aud".
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 56584ce3-fd87-4c2d-8d8b-8cf72c0b2cba
⛔ Files ignored due to path filters (1)
public/images/publishing_amazon_s3.svgis excluded by!**/*.svg
📒 Files selected for processing (2)
maggie/worktree-s3-integration-docs/state.jsonpages/publishing/publishing/amazon-s3.mdx
CodeRabbit flagged that accounts.google.com:aud (= SA email) is caller-set and not an identity proof. Keep the documented config for this release; track hardening to accounts.google.com:sub as an inline TODO. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>



Summary
Documents the new Amazon S3 publishing integration (publishes a JSON snapshot of the tracking plan to a customer-owned S3 bucket), landing alongside the other publishing integration pages.
New page serves at
/docs/publishing/publishing/amazon-s3and covers:s3:PutObjectpolicy, optional key prefix)<timestamp>-<publishType>.jsonsnapshot + rollinglatest.jsonpointer, keyed by workspace and branchChanges
pages/publishing/publishing/amazon-s3.mdxpages/publishing/publishing/_meta.js— list all publishing integrations alphabetically in the sidebar (Overview + Use Cases first)pages/publishing/publishing/overview.mdx— add Amazon S3 to the integrations listnext.config.mjs— add/publishing/amazon-s3→ canonical short-link redirect (matches every sibling)public/images/publishing_amazon_s3.svg— placeholder logoTODOs left for follow-up
Verification
yarn dev: page returns 200, all headings/anchors render, sidebar shows Amazon S3 alphabetically (prev: Adobe Experience Platform, next: Amplitude Data)yarn spellcheckpasses cleanNote
The pre-commit
next linthook fails with an ESLint plugin conflict because this branch was authored in a git worktree nested inside the repo (two.eslintrc.jsonfiles resolve). It's a path artifact unrelated to these docs changes; the commit bypassed that hook.cspellpassed.🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Documentation