Skip to content

Add Tenzir v6 migration guide#293

Merged
mavam merged 12 commits intotopic/new-executorfrom
topic/neo-migration-guide
May 7, 2026
Merged

Add Tenzir v6 migration guide#293
mavam merged 12 commits intotopic/new-executorfrom
topic/neo-migration-guide

Conversation

@mavam
Copy link
Copy Markdown
Member

@mavam mavam commented May 7, 2026

🔍 Problem

  • Customers need a clear migration path before Tenzir v6 makes the new engine the default.
  • The temporary compatibility controls and pipeline changes were not documented in one high-visibility guide.
  • Existing docs still contained copyable examples and references for the removed generic from and to operators.

🛠️ Solution

  • Add a Tenzir v6 migration guide with migration modes, compatibility controls, a checklist, v6 execution patterns, migration reference tables, and before/after examples.
  • Add the guide to Guides → Get Started and cross-link it from the affected operator references.
  • Clarify subpipelines as a first-class v6 pattern in the programs reference.
  • Replace legacy from/to examples across docs with named source and sink operators, and remove the obsolete from/to reference pages/cards.

💬 Review

  • This PR is stacked on topic/new-executor, because the migration guide links to and builds on the new executor/operator documentation there.
  • Please focus on the migration reference for completeness and on the exact wording around neo: false, // neo, and //neo:false.
  • Please also review the chosen replacements for the removed generic from and to examples, especially AMQP, SQS, TCP, and UDP examples.
✅ Closes TNZ-523

@github-actions github-actions Bot added guide How-to guides tutorial Tutorials explanation Explanations reference Reference documentation integration Integration documentation site Site infrastructure labels May 7, 2026
@mavam mavam changed the base branch from main to topic/new-executor May 7, 2026 14:37
@mavam mavam force-pushed the topic/neo-migration-guide branch from c31570e to 94dd6c3 Compare May 7, 2026 14:38
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 7, 2026

📦 Preview  ·  🟠 Still propagating

The deploy completed, but the public URL has not served build 64d414b yet. Check again in a minute.

@mavam mavam force-pushed the topic/neo-migration-guide branch 3 times, most recently from e80be87 to a0c8eba Compare May 7, 2026 15:01
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread src/content/docs/reference/operators.mdx Outdated
@mavam mavam force-pushed the topic/neo-migration-guide branch from a0c8eba to f29ba11 Compare May 7, 2026 17:39
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread src/content/docs/reference/operators.mdx
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)
@mavam mavam force-pushed the topic/neo-migration-guide branch from f29ba11 to 126f755 Compare May 7, 2026 18:27
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread src/content/docs/guides/tenzir-v6-migration.mdx Outdated
mavam added 7 commits May 7, 2026 20:32
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)
@mavam mavam force-pushed the topic/neo-migration-guide branch from cf1456f to bef5fa4 Compare May 7, 2026 18:52
mavam added 4 commits May 7, 2026 20:56
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)
@mavam mavam merged commit a94906f into topic/new-executor May 7, 2026
5 checks passed
@mavam mavam deleted the topic/neo-migration-guide branch May 7, 2026 19:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

explanation Explanations guide How-to guides integration Integration documentation reference Reference documentation site Site infrastructure tutorial Tutorials

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant