Document Terraform redpanda_pipeline resource and Connect egress allowlist#641
Document Terraform redpanda_pipeline resource and Connect egress allowlist#641david-yu wants to merge 2 commits into
Conversation
…wlist Add a "Create Redpanda Connect pipelines" section to the Terraform provider page (above "Manage cluster secrets"), covering the redpanda_pipeline resource and the new redpanda_connect.allowed_destination_cidr_ports egress allowlist (provider v2.1.1+). Add a BYOC egress allowlist section to the Connect quickstart and a What's New entry. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
✅ Deploy Preview for rp-cloud ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
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: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughAdds documentation for creating Redpanda Connect pipelines with Terraform and configuring BYOC outbound egress allowlists through Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 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 `@modules/manage/pages/terraform-provider.adoc`:
- Line 390: Update the Redpanda provider version constraints in the setup block
and all BYOC, Dedicated, and Serverless example snippets from ~> 1.0 to a
constraint allowing version 2.1.1 or newer, ensuring examples using
redpanda_connect.allowed_destination_cidr_ports are installable.
🪄 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: CHILL
Plan: Pro
Run ID: 9378219e-b466-4d66-82e7-e445139aa7d6
📒 Files selected for processing (3)
modules/develop/pages/connect/connect-quickstart.adocmodules/get-started/pages/whats-new-cloud.adocmodules/manage/pages/terraform-provider.adoc
…= 2.1.1 - Trim learning objectives to three: create a BYOC cluster, enable Redpanda SQL, and create Redpanda Connect pipelines with egress - Bump provider version pins from ~> 1.0 to >= 2.1.1 so examples using redpanda_connect.allowed_destination_cidr_ports are installable - Use "data plane" and "publicly routable" per reviewer suggestion Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Description
Documents the
redpanda_pipelineresource and the newredpanda_connect.allowed_destination_cidr_portsegress allowlist, released in Redpanda Terraform provider v2.1.1 (terraform-provider-redpanda#359).redpanda_pipelineexample, attribute descriptions, and a note on escaping${...}secret/contextual-variable references as$${...}in HCL heredocs. Includes an "Enable egress to custom destinations" subsection documenting the CIDR+port allowlist (up to 16 rules, in-place update, single-port rules omitport_end), the network-path caveat (allowlist does not replace VPC peering/routes), and an end-to-endsql_insert-to-private-PostgreSQL pipeline example. Added a fifth learning objective.Review deadline:
Preview pages
Checks