Add Tenzir v6 migration guide#293
Conversation
c31570e to
94dd6c3
Compare
|
📦 Preview · 🟠 Still propagating The deploy completed, but the public URL has not served build |
e80be87 to
a0c8eba
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a0c8eba6f6
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
a0c8eba to
f29ba11
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f29ba118ae
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Document the Tenzir v6 pipeline migration path, including compatibility controls, migration modes, new execution patterns, and the quick-scan table for legacy pipeline changes. Assisted-by: GPT-5 (Codex)
f29ba11 to
126f755
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 126f755e27
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Remove metadata entries for deleted legacy operator pages and render legacy-only operator names as code to avoid dead semantic links. Assisted-by: GPT-5 (pi)
Split details and summary tags onto separate lines so MDX parses the disclosure blocks correctly after the reflow pass. Assisted-by: GPT-5 (pi)
Remove legacy migration notes from regular docs and update examples to use the current dedicated operators. Keep version-specific guidance in the migration guide. Assisted-by: GPT-5 (pi)
Document the OpenSearch operators as the supported Bulk API path for both OpenSearch and Elasticsearch. Replace stale to_elasticsearch and from_opensearch examples, fix option names, and keep the Fluent Bit integration on Fluent Bit plugins. Assisted-by: ChatGPT (pi)
cf1456f to
bef5fa4
Compare
Add the required message argument to the Pub/Sub destination guide and remove stale byte-stream Pub/Sub cards from the operator index. Assisted-by: ChatGPT (pi)
Order the operator categories and cards alphabetically. Remove redundant subcategory headings now that event and byte subsections no longer differ. Assisted-by: ChatGPT (pi)
Remove the extra trailing blank line that trips markdownlint in CI. Assisted-by: GPT-5.1 Codex Max (pi)
🔍 Problem
fromandtooperators.🛠️ Solution
from/toexamples across docs with named source and sink operators, and remove the obsoletefrom/toreference pages/cards.💬 Review
- This PR is stacked on
- Please focus on the migration reference for completeness and on the exact wording around
- Please also review the chosen replacements for the removed generic
✅ Closes TNZ-523topic/new-executor, because the migration guide links to and builds on the new executor/operator documentation there.neo: false,// neo, and//neo:false.fromandtoexamples, especially AMQP, SQS, TCP, and UDP examples.