Improve RDI pipeline configuration guide

[ZdravkoDonev-redis]

What changed

• start with a minimal config.yaml example and move the complete example to the end
• add a copyable AI prompt that restricts generated configuration to documented properties
• organize prerequisites and link to the full configuration reference
• document the supported single target named target
• align source collector options and connection field names with the current public reference

Why

The current page begins with a large configuration that mixes required and optional properties. This makes it difficult to identify the smallest working file and gives AI assistants too much room to infer unsupported configuration.

The revised page gives readers a minimal starting point, then keeps the detailed options available for reference. It also removes the suggestion that multiple target databases are supported, even though the configuration schema accepts multiple target entries.

Fact-checking

Compared the page with:

• rdi_utils/src/redis_di_utils/resources/schemas/config.schema.json in redis-data-integration
• the generated RDI config.yaml reference in this repository
• current deployment and database preparation documentation

Validation

• git diff --check
• Hugo processed the updated content and relrefs. The full-site build later stopped on an unrelated existing docs-nav.html error: can't evaluate field ByWeight in type []interface {}.

Review focus

Please comment on product facts or wording that still needs an RDI owner decision. In particular, review the AI prompt constraints and the public single-target statement.

---

Note

Low Risk
Documentation-only changes to a single Hugo page; product behavior is unchanged, though the single-target and collector-type statements should be confirmed by an RDI owner as noted in the PR.

Overview
Restructures the RDI config.yaml pipeline configuration page so readers start from a minimal working example and add optional settings incrementally, with prerequisites and a link to the full reference up front.

Adds a copy-paste AI assistant prompt that limits answers to documented properties, enforces Flink and a single target named target, and walks through required inputs. Sources documentation now lists collector types (cdc, flink, riotx, external) and uses user/password for connections. Targets are documented as one Redis database named target (removing prior wording about multiple target connections). Processors content is split into focused subsections (Classic vs Flink tuning, target_data_type, replica wait) with Flink as the default for new pipelines; the large commented example moves to an Extended configuration example at the end. The localhost/k3s troubleshooting note is removed from this page.

^{Reviewed by Cursor Bugbot for commit ec04e45. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

🧠 Redis Memory

Found 9 related items from repository history:

• PR — RC RDI: GA flow

• PR — DOC-6833: Fix four RDI Cloud doc issues from #rdi-cloud

  • Remove Active-Active from the 'multiple targets' use case sentence; add it as an explicit unsupported target topology under 'When not to u

• PR — DOC-6745 RDI: remove redundancies and restructure

  NOTE: not finished - this is just to get early feedback from the Bugbot.

• PR — DOC-5750 clearer pointers about using RDI in Redis Insight

  We've had some feedback saying that the [RDI K8s install page](https://redis.io/docs/latest/integrate/redis-data-integration/installation/in

• PR — Document RDI rejected records

  Summary

• Commit — Improve RDI pipeline configuration guide

  Improve RDI pipeline configuration guide

• PR — RDSC-4603 Update RDI public documentation

  See https://redislabs.atlassian.net/browse/RDSC-4603 and https://github.com/RedisLabs/redis-data-integration/pull/2565

• PR — DOC-6711 RDI config reference ideas

  WIP: don't merge yet!

• PR — DOC-6711 RDI config reference ideas

  WIP: don't merge yet!

Memory updated at ec04e45

[github-actions]

Staging links:
https://redis.io/docs/staging/agent/rdi-pipeline-config-digestible/integrate/redis-data-integration/data-pipelines/pipeline-config/