Driver: Add page about Rust

[amotl]

About

What the title says.

Preview

https://cratedb-guide--407.org.readthedocs.build/connect/rust/

[coderabbitai]

Walkthrough

Documentation for Rust driver support is added to the CrateDB guide. A new Rust connection documentation page is created with examples for localhost and CrateDB Cloud. The driver index and configuration are updated to include Rust.

Changes

Cohort / File(s)	Change Summary
Driver Documentation Index docs/connect/index.md	Adds Rust driver card to the drivers grid with connect-rust link, alt text, and Rust icon. Updates toctree to include Rust entry.
Rust Connection Guide docs/connect/rust/index.md	New documentation page with Rust driver overview, localhost connection example using postgres crate, Docker/Podman setup instructions, CrateDB Cloud example with TLS support, project initialization steps, and GitHub examples card.
Link Checking Configuration docs/conf.py	Adds r"https://crates.io/crates/" to linkcheck_ignore list with preceding comment about 404 errors.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• crate/cratedb-guide#237: Restructures and renames cards and driver references in docs/connect/index.md, directly related to driver grid modifications.
• crate/cratedb-guide#361: Modifies docs/connect/index.md's drivers grid and toctree with driver card and navigation updates.
• crate/cratedb-guide#338: Updates docs/connect/index.md's drivers grid with new driver cards and references.

Suggested labels

new content

Suggested reviewers

• kneth
• surister
• bmunkholm

Poem

🐰 A Rust card joins the driver array,
With postgres examples to light the way,
From localhost to CrateDB Cloud so bright,
Connection strings shimmer with TLS might!
New docs hop forth with examples in tow. ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description Check	❓ Inconclusive	The PR description provided is "What the title says," which is an extremely vague and non-descriptive phrase that does not convey meaningful information about the changeset on its own. While the description can be inferred to relate to the changeset when combined with the PR title "Driver: Add page about Rust," the description itself relies entirely on the title to be understood and contains no substantive details about the changes made. The description uses non-descriptive language and does not stand alone as a meaningful explanation of what was changed.	Consider requesting that the author expand the description to include specific details about what was added to the Rust documentation, such as mentioning the new documentation page, driver card, configuration changes, or other key updates. A more descriptive PR description helps reviewers and future maintainers understand the intent and scope of the changes without needing to infer meaning from the title alone.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title "Driver: Add page about Rust" is directly related to the main changes in the changeset. The modifications add a new Rust driver documentation page (docs/connect/rust/index.md), include a Rust driver card in the index, and update configuration files to support Rust documentation. The title is concise, specific, and uses a clear convention prefix ("Driver:") that would help teammates quickly understand the primary change when scanning history. The phrasing avoids vague or generic terms and accurately captures the intent of the changeset.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch rust

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}