Skip to content

Document the Terraform provider - #483

Open
IlyaasK wants to merge 1 commit into
mainfrom
hypeship/add-terraform-provider-docs
Open

Document the Terraform provider#483
IlyaasK wants to merge 1 commit into
mainfrom
hypeship/add-terraform-provider-docs

Conversation

@IlyaasK

@IlyaasK IlyaasK commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add a concise Terraform integration page to the public documentation
  • link to the Terraform Registry for installation and generated reference docs
  • link to GitHub for examples, releases, source, and contributions
  • add the page to the sidebar and integrations overview

Why

Kernel Terraform Provider v0.1 is publicly available. Customers need a discoverable path from Kernel documentation without duplicating the provider reference documentation maintained by the Registry and provider repository.

Scope

The page documents durable infrastructure management only. It directs runtime browser operations to Kernel SDKs and APIs.

Verification

  • python3 -m json.tool docs.json
  • bunx --bun mint broken-links
  • verified https://registry.terraform.io/providers/kernel/kernel/latest returns HTTP 200
  • reviewed the rendered MDX structure and navigation entry locally

Note

Low Risk
Documentation and navigation only; no application or infrastructure code changes.

Overview
Adds a Terraform integration guide so customers can find the official kernel/kernel provider from Kernel docs after v0.1 went public.

The new page covers minimal required_providers / provider setup, KERNEL_API_KEY and optional KERNEL_PROJECT_ID, and clarifies that Terraform is for durable config (projects, browser pools, imports) while runtime browser work stays on SDKs/API. It links out to the Terraform Registry and GitHub for full reference instead of duplicating provider docs.

Navigation is wired via docs.json (Integrations sidebar) and a bullet on integrations/overview.mdx.

Reviewed by Cursor Bugbot for commit aedc9dc. Bugbot is set up for automated code reviews on this repo. Configure here.

@mintlify

mintlify Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
Kernel 🟢 Ready View Preview Aug 5, 2026, 9:21 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@vercel

vercel Bot commented Aug 5, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
docs Error Error Aug 5, 2026 9:20pm

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Risk Assessment: Very Low

Verdict: Safe to approve.

What changed (from the diff)

  • Added integrations/terraform.mdx — a short public docs page describing the Kernel Terraform provider, env vars, and links to the Terraform Registry / GitHub
  • Added one Integrations sidebar entry in docs.json
  • Added one bullet link on integrations/overview.mdx

Why this is Very Low risk

  • Documentation-only Mintlify content and navigation wiring
  • Small, additive diff (+41 / −0) with no application, auth, billing, or infrastructure code
  • No shared runtime systems or production logic modified
  • Blast radius limited to docs discoverability for an existing public provider

Checks

  • No CODEOWNERS file requiring a human owner approval path
  • No prior approvals on this PR
  • No reviewers assigned or requested by this assessment
Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

@andrewleesteele andrewleesteele left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

lgtm

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.

2 participants