mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-01 13:18:10 +00:00
* feat: adopt directory-based docs versioning with Edge channel Switch docs.crewai.com from navigation-only versioning (every version selector entry rendered the same docs/<lang>/* source files) to Mintlify's directory-based versioning so each version selector entry renders its own snapshot. Add an "Edge" channel under docs/edge/<lang>/* that always reflects main HEAD for unreleased work, eliminating pre-release leakage onto frozen release labels. External links to canonical /<lang>/* URLs are preserved via wildcard redirects that always land on the current default version. Layout: - docs/edge/<lang>/* rolling source (you edit here) - docs/edge/enterprise-api.*.yaml - docs/v<X.Y.Z>/<lang>/* frozen, immutable snapshots - docs/v<X.Y.Z>/enterprise-api.*.yaml - docs/images/ shared, append-only - docs/docs.json nav + redirects URLs follow the Mintlify-idiomatic shape: /edge/<lang>/<page> for Edge, /v<X.Y.Z>/<lang>/<page> for every frozen snapshot. The wildcard redirects /<lang>/:slug* -> /<default>/<lang>/:slug* keep stale links working, and every freeze rewrites them (plus all per-section/per-page redirects) so destinations always resolve to the current default without depending on a second redirect hop. Release flow integration (devtools release): - New module crewai_devtools.docs_versioning.freeze() materialises docs/v<X.Y.Z>/ from docs/edge/, rewrites openapi: refs inside the snapshot, inserts the version into every language block in docs.json, and refreshes all redirect destinations. - _update_docs_and_create_pr() in cli.py now calls that freeze during Phase 2 of devtools release. Edge changelogs are updated first (so the snapshot freeze picks them up), then the snapshot is staged alongside docs.json, branched as docs/freeze-v<X.Y.Z>, and the PR is titled [docs-freeze] docs: snapshot and changelog for v<X.Y.Z> — the title prefix the new CI guard reads. - The PR still gates tag, GitHub release, PyPI publish, and the enterprise release as before; no new PRs are added. - Pre-releases (1.X.YaN, 1.X.YbN, ...) skip the snapshot — they ride Edge — and the docs PR title omits the [docs-freeze] prefix. - docs_check (AI-generated docs scaffolding) writes to docs/edge/<lang>/* so newly-generated unreleased docs land in Edge and never accidentally touch a frozen snapshot. Migration scripts (one-shot): - scripts/docs/freeze_historical_versions.py reconstructs all 16 historical snapshots (v1.10.0 .. v1.14.7) from git tags via git archive | tar, rewriting openapi: MDX refs so each snapshot reads its own enterprise-api YAML rather than the live one. - scripts/docs/prefix_version_paths.py one-shot-migrates docs.json: rewrites every page path in 16 versioned blocks to point under docs/v<X.Y.Z>/, inserts a new Edge entry per language, tags v1.14.7 as Latest (default), prunes pages whose target file doesn't exist in the snapshot (e.g. docs/ar/ didn't exist before v1.12.0), and writes the wildcard + per-section redirects. - scripts/docs/freeze_current_edge.py is now a thin CLI wrapper around docs_versioning.freeze for manual one-off freezes (e.g. retroactively snapshotting a forgotten release). CI guards (.github/workflows/docs-snapshots.yml): - Frozen snapshots under docs/v[0-9]*/ are immutable; only PRs whose title contains [docs-freeze] (i.e. release-cut PRs generated by devtools release or the manual wrapper) may modify them. - Images under docs/images/ are append-only since snapshots share a single image directory. Deleting or renaming an image breaks every historical snapshot that still references it. Restored docs/images/crewai-otel-export.png from PR #3673; it was deleted in PR #4908 but v1.10.0 / v1.10.1 snapshots still reference it. Restoring instead of editing the snapshots preserves historical rendering fidelity and validates the new append-only rule retroactively. Tests: - lib/devtools/tests/test_docs_versioning.py covers the freeze: file copy, openapi rewrite, version insertion, default demotion, redirect upserts, per-section redirect rewriting, idempotency, and invalid inputs. Verified locally with mintlify broken-links: 0 broken links across the full site (Edge + 16 frozen versions, 4 locales). AGENTS.md (repo root) is the contributor guide for the new model; RELEASING.md is the release-cut runbook; README's Contribution section links to both. Co-authored-by: Cursor <cursoragent@cursor.com> * style: resolve linter issues --------- Co-authored-by: Cursor <cursoragent@cursor.com>
203 lines
7.0 KiB
Plaintext
203 lines
7.0 KiB
Plaintext
---
|
|
title: Snowflake Search Tool
|
|
description: The `SnowflakeSearchTool` enables CrewAI agents to execute SQL queries and perform semantic search on Snowflake data warehouses.
|
|
icon: snowflake
|
|
mode: "wide"
|
|
---
|
|
|
|
# `SnowflakeSearchTool`
|
|
|
|
## Description
|
|
|
|
The `SnowflakeSearchTool` is designed to connect to Snowflake data warehouses and execute SQL queries with advanced features like connection pooling, retry logic, and asynchronous execution. This tool allows CrewAI agents to interact with Snowflake databases, making it ideal for data analysis, reporting, and business intelligence tasks that require access to enterprise data stored in Snowflake.
|
|
|
|
## Installation
|
|
|
|
To use this tool, you need to install the required dependencies:
|
|
|
|
```shell
|
|
uv add cryptography snowflake-connector-python snowflake-sqlalchemy
|
|
```
|
|
|
|
Or alternatively:
|
|
|
|
```shell
|
|
uv sync --extra snowflake
|
|
```
|
|
|
|
## Steps to Get Started
|
|
|
|
To effectively use the `SnowflakeSearchTool`, follow these steps:
|
|
|
|
1. **Install Dependencies**: Install the required packages using one of the commands above.
|
|
2. **Configure Snowflake Connection**: Create a `SnowflakeConfig` object with your Snowflake credentials.
|
|
3. **Initialize the Tool**: Create an instance of the tool with the necessary configuration.
|
|
4. **Execute Queries**: Use the tool to run SQL queries against your Snowflake database.
|
|
|
|
## Example
|
|
|
|
The following example demonstrates how to use the `SnowflakeSearchTool` to query data from a Snowflake database:
|
|
|
|
```python Code
|
|
from crewai import Agent, Task, Crew
|
|
from crewai_tools import SnowflakeSearchTool, SnowflakeConfig
|
|
|
|
# Create Snowflake configuration
|
|
config = SnowflakeConfig(
|
|
account="your_account",
|
|
user="your_username",
|
|
password="your_password",
|
|
warehouse="COMPUTE_WH",
|
|
database="your_database",
|
|
snowflake_schema="your_schema"
|
|
)
|
|
|
|
# Initialize the tool
|
|
snowflake_tool = SnowflakeSearchTool(config=config)
|
|
|
|
# Define an agent that uses the tool
|
|
data_analyst_agent = Agent(
|
|
role="Data Analyst",
|
|
goal="Analyze data from Snowflake database",
|
|
backstory="An expert data analyst who can extract insights from enterprise data.",
|
|
tools=[snowflake_tool],
|
|
verbose=True,
|
|
)
|
|
|
|
# Example task to query sales data
|
|
query_task = Task(
|
|
description="Query the sales data for the last quarter and summarize the top 5 products by revenue.",
|
|
expected_output="A summary of the top 5 products by revenue for the last quarter.",
|
|
agent=data_analyst_agent,
|
|
)
|
|
|
|
# Create and run the crew
|
|
crew = Crew(agents=[data_analyst_agent],
|
|
tasks=[query_task])
|
|
result = crew.kickoff()
|
|
```
|
|
|
|
You can also customize the tool with additional parameters:
|
|
|
|
```python Code
|
|
# Initialize the tool with custom parameters
|
|
snowflake_tool = SnowflakeSearchTool(
|
|
config=config,
|
|
pool_size=10,
|
|
max_retries=5,
|
|
retry_delay=2.0,
|
|
enable_caching=True
|
|
)
|
|
```
|
|
|
|
## Parameters
|
|
|
|
### SnowflakeConfig Parameters
|
|
|
|
The `SnowflakeConfig` class accepts the following parameters:
|
|
|
|
- **account**: Required. Snowflake account identifier.
|
|
- **user**: Required. Snowflake username.
|
|
- **password**: Optional*. Snowflake password.
|
|
- **private_key_path**: Optional*. Path to private key file (alternative to password).
|
|
- **warehouse**: Required. Snowflake warehouse name.
|
|
- **database**: Required. Default database.
|
|
- **snowflake_schema**: Required. Default schema.
|
|
- **role**: Optional. Snowflake role.
|
|
- **session_parameters**: Optional. Custom session parameters as a dictionary.
|
|
|
|
*Either `password` or `private_key_path` must be provided.
|
|
|
|
### SnowflakeSearchTool Parameters
|
|
|
|
The `SnowflakeSearchTool` accepts the following parameters during initialization:
|
|
|
|
- **config**: Required. A `SnowflakeConfig` object containing connection details.
|
|
- **pool_size**: Optional. Number of connections in the pool. Default is 5.
|
|
- **max_retries**: Optional. Maximum retry attempts for failed queries. Default is 3.
|
|
- **retry_delay**: Optional. Delay between retries in seconds. Default is 1.0.
|
|
- **enable_caching**: Optional. Whether to enable query result caching. Default is True.
|
|
|
|
## Usage
|
|
|
|
When using the `SnowflakeSearchTool`, you need to provide the following parameters:
|
|
|
|
- **query**: Required. The SQL query to execute.
|
|
- **database**: Optional. Override the default database specified in the config.
|
|
- **snowflake_schema**: Optional. Override the default schema specified in the config.
|
|
- **timeout**: Optional. Query timeout in seconds. Default is 300.
|
|
|
|
The tool will return the query results as a list of dictionaries, where each dictionary represents a row with column names as keys.
|
|
|
|
```python Code
|
|
# Example of using the tool with an agent
|
|
data_analyst = Agent(
|
|
role="Data Analyst",
|
|
goal="Analyze sales data from Snowflake",
|
|
backstory="An expert data analyst with experience in SQL and data visualization.",
|
|
tools=[snowflake_tool],
|
|
verbose=True
|
|
)
|
|
|
|
# The agent will use the tool with parameters like:
|
|
# query="SELECT product_name, SUM(revenue) as total_revenue FROM sales GROUP BY product_name ORDER BY total_revenue DESC LIMIT 5"
|
|
# timeout=600
|
|
|
|
# Create a task for the agent
|
|
analysis_task = Task(
|
|
description="Query the sales database and identify the top 5 products by revenue for the last quarter.",
|
|
expected_output="A detailed analysis of the top 5 products by revenue.",
|
|
agent=data_analyst
|
|
)
|
|
|
|
# Run the task
|
|
crew = Crew(
|
|
agents=[data_analyst],
|
|
tasks=[analysis_task]
|
|
)
|
|
result = crew.kickoff()
|
|
```
|
|
|
|
## Advanced Features
|
|
|
|
### Connection Pooling
|
|
|
|
The `SnowflakeSearchTool` implements connection pooling to improve performance by reusing database connections. You can control the pool size with the `pool_size` parameter.
|
|
|
|
### Automatic Retries
|
|
|
|
The tool automatically retries failed queries with exponential backoff. You can configure the retry behavior with the `max_retries` and `retry_delay` parameters.
|
|
|
|
### Query Result Caching
|
|
|
|
To improve performance for repeated queries, the tool can cache query results. This feature is enabled by default but can be disabled by setting `enable_caching=False`.
|
|
|
|
### Key-Pair Authentication
|
|
|
|
In addition to password authentication, the tool supports key-pair authentication for enhanced security:
|
|
|
|
```python Code
|
|
config = SnowflakeConfig(
|
|
account="your_account",
|
|
user="your_username",
|
|
private_key_path="/path/to/your/private/key.p8",
|
|
warehouse="COMPUTE_WH",
|
|
database="your_database",
|
|
snowflake_schema="your_schema"
|
|
)
|
|
```
|
|
|
|
## Error Handling
|
|
|
|
The `SnowflakeSearchTool` includes comprehensive error handling for common Snowflake issues:
|
|
|
|
- Connection failures
|
|
- Query timeouts
|
|
- Authentication errors
|
|
- Database and schema errors
|
|
|
|
When an error occurs, the tool will attempt to retry the operation (if configured) and provide detailed error information.
|
|
|
|
## Conclusion
|
|
|
|
The `SnowflakeSearchTool` provides a powerful way to integrate Snowflake data warehouses with CrewAI agents. With features like connection pooling, automatic retries, and query caching, it enables efficient and reliable access to enterprise data. This tool is particularly useful for data analysis, reporting, and business intelligence tasks that require access to structured data stored in Snowflake. |