Skip to content

Automate the enterprise front-matter flag - #611

Open
kacperlukawski wants to merge 1 commit into
mainfrom
add-enterprise-flag-automation
Open

kacperlukawski wants to merge 1 commit into
mainfrom
add-enterprise-flag-automation

Conversation

@kacperlukawski

Copy link
Copy Markdown
Member

Summary

  • Adds scripts/update_enterprise_flags.py, which cross-references each integration page's name against the partner sections of deepset-ai/haystack's Haystack Enterprise Components table (docs-website/docs/overview/platform-components.mdx), and sets enterprise: true on any page that matches. That table is generated nightly by haystack's scripts/generate_platform_components_table.py and is public, so this needs no dependency installs, no private API access, and no code-sample parsing.
  • Adds .github/workflows/update-enterprise-flags.yml, a nightly workflow (offset after haystack's own 02:00 UTC run) that runs the script and opens a PR with any changes, same pattern as haystack's update-platform-components bot workflow.
  • Includes the initial backfill: 78 of 82 platform partners matched to an integration page and got enterprise: true. The remaining 4 (Amazon S3, Azure DocumentDB, Transformers, Unstructured) have no single unambiguous corresponding page — the script logs them as warnings instead of guessing.
  • A small PARTNER_NAME_ALIASES table covers the handful of partner names that don't match their integration page's name field case-insensitively (e.g. "AIML API" → "AIMLAPI", "Astra" → "AstraDB").

Test plan

  • Dry-run and real-write tested against a sandbox copy of integrations/ and the full real directory
  • Verified idempotency (second run makes zero changes)
  • Verified each changed file gained exactly one clean enterprise: true line, nothing else touched
  • Spot-checked several diffs by hand

🤖 Generated with Claude Code

Adds scripts/update_enterprise_flags.py and a nightly GitHub Actions
workflow that cross-reference each integration page's `name` against
the partner sections of deepset-ai/haystack's Haystack Enterprise
Components table (docs-website/docs/overview/platform-components.mdx,
generated nightly there by scripts/generate_platform_components_table.py),
and set `enterprise: true` on any page that matches.

The matching is purely by partner name against a public, pre-generated
page - no dependency installs, no private API access, no code-sample
parsing. A small alias table covers partner names that don't match
their integration page's `name` field case-insensitively.

Includes the initial backfill: 78 of 82 platform partners matched to
an integration page. The remaining 4 (Amazon S3, Azure DocumentDB,
Transformers, Unstructured) have no unambiguous corresponding page and
are logged as warnings rather than guessed.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@kacperlukawski
kacperlukawski requested a review from a team as a code owner September 18, 2026 12:53
@vercel

vercel Bot commented Sep 18, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
haystack-integrations Ready Ready Preview Sep 18, 2026 12:54pm UTC

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant