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>
152 lines
6.1 KiB
Plaintext
152 lines
6.1 KiB
Plaintext
---
|
|
title: أداة كتابة S3
|
|
description: تمكّن `S3WriterTool` وكلاء CrewAI من كتابة المحتوى إلى ملفات في حاويات Amazon S3.
|
|
icon: aws
|
|
mode: "wide"
|
|
---
|
|
|
|
# `S3WriterTool`
|
|
|
|
## الوصف
|
|
|
|
صُممت `S3WriterTool` لكتابة المحتوى إلى ملفات في حاويات Amazon S3. تتيح هذه الأداة لوكلاء CrewAI إنشاء أو تحديث الملفات في S3، مما يجعلها مثالية لسير العمل الذي يتطلب تخزين البيانات أو حفظ ملفات الإعداد أو حفظ أي محتوى آخر في تخزين AWS S3.
|
|
|
|
## التثبيت
|
|
|
|
لاستخدام هذه الأداة، تحتاج إلى تثبيت التبعيات المطلوبة:
|
|
|
|
```shell
|
|
uv add boto3
|
|
```
|
|
|
|
## خطوات البدء
|
|
|
|
لاستخدام `S3WriterTool` بفعالية، اتبع الخطوات التالية:
|
|
|
|
1. **تثبيت التبعيات**: ثبّت الحزم المطلوبة باستخدام الأمر أعلاه.
|
|
2. **إعداد بيانات اعتماد AWS**: عيّن بيانات اعتماد AWS كمتغيرات بيئة.
|
|
3. **تهيئة الأداة**: أنشئ مثيلاً من الأداة.
|
|
4. **تحديد مسار S3 والمحتوى**: قدّم مسار S3 حيث تريد كتابة الملف والمحتوى المراد كتابته.
|
|
|
|
## مثال
|
|
|
|
يوضح المثال التالي كيفية استخدام `S3WriterTool` لكتابة محتوى إلى ملف في حاوية S3:
|
|
|
|
```python Code
|
|
from crewai import Agent, Task, Crew
|
|
from crewai_tools.aws.s3 import S3WriterTool
|
|
|
|
# Initialize the tool
|
|
s3_writer_tool = S3WriterTool()
|
|
|
|
# Define an agent that uses the tool
|
|
file_writer_agent = Agent(
|
|
role="File Writer",
|
|
goal="Write content to files in S3 buckets",
|
|
backstory="An expert in storing and managing files in cloud storage.",
|
|
tools=[s3_writer_tool],
|
|
verbose=True,
|
|
)
|
|
|
|
# Example task to write a report
|
|
write_task = Task(
|
|
description="Generate a summary report of the quarterly sales data and save it to {my_bucket}.",
|
|
expected_output="Confirmation that the report was successfully saved to S3.",
|
|
agent=file_writer_agent,
|
|
)
|
|
|
|
# Create and run the crew
|
|
crew = Crew(agents=[file_writer_agent], tasks=[write_task])
|
|
result = crew.kickoff(inputs={"my_bucket": "s3://my-bucket/reports/quarterly-summary.txt"})
|
|
```
|
|
|
|
## المعاملات
|
|
|
|
تقبل `S3WriterTool` المعاملات التالية عند استخدامها من قبل وكيل:
|
|
|
|
- **file_path**: مطلوب. مسار ملف S3 بتنسيق `s3://bucket-name/file-name`.
|
|
- **content**: مطلوب. المحتوى المراد كتابته في الملف.
|
|
|
|
## بيانات اعتماد AWS
|
|
|
|
تتطلب الأداة بيانات اعتماد AWS للوصول إلى حاويات S3. يمكنك إعداد هذه البيانات باستخدام متغيرات البيئة:
|
|
|
|
- **CREW_AWS_REGION**: منطقة AWS حيث تقع حاوية S3. القيمة الافتراضية `us-east-1`.
|
|
- **CREW_AWS_ACCESS_KEY_ID**: معرّف مفتاح الوصول لـ AWS.
|
|
- **CREW_AWS_SEC_ACCESS_KEY**: مفتاح الوصول السري لـ AWS.
|
|
|
|
## الاستخدام
|
|
|
|
عند استخدام `S3WriterTool` مع وكيل، سيحتاج الوكيل لتقديم كل من مسار ملف S3 والمحتوى المراد كتابته:
|
|
|
|
```python Code
|
|
# Example of using the tool with an agent
|
|
file_writer_agent = Agent(
|
|
role="File Writer",
|
|
goal="Write content to files in S3 buckets",
|
|
backstory="An expert in storing and managing files in cloud storage.",
|
|
tools=[s3_writer_tool],
|
|
verbose=True,
|
|
)
|
|
|
|
# Create a task for the agent to write a specific file
|
|
write_config_task = Task(
|
|
description="""
|
|
Create a configuration file with the following database settings:
|
|
- host: db.example.com
|
|
- port: 5432
|
|
- username: app_user
|
|
- password: secure_password
|
|
|
|
Save this configuration as JSON to {my_bucket}.
|
|
""",
|
|
expected_output="Confirmation that the configuration file was successfully saved to S3.",
|
|
agent=file_writer_agent,
|
|
)
|
|
|
|
# Run the task
|
|
crew = Crew(agents=[file_writer_agent], tasks=[write_config_task])
|
|
result = crew.kickoff(inputs={"my_bucket": "s3://my-bucket/config/db-config.json"})
|
|
```
|
|
|
|
## معالجة الأخطاء
|
|
|
|
تتضمن `S3WriterTool` معالجة أخطاء لمشكلات S3 الشائعة:
|
|
|
|
- تنسيق مسار S3 غير صالح
|
|
- مشكلات الأذونات (مثل عدم وجود صلاحية كتابة للحاوية)
|
|
- مشكلات بيانات اعتماد AWS
|
|
- الحاوية غير موجودة
|
|
|
|
عند حدوث خطأ، ستعيد الأداة رسالة خطأ تتضمن تفاصيل حول المشكلة.
|
|
|
|
## تفاصيل التنفيذ
|
|
|
|
تستخدم `S3WriterTool` حزمة AWS SDK لـ Python (boto3) للتفاعل مع S3:
|
|
|
|
```python Code
|
|
class S3WriterTool(BaseTool):
|
|
name: str = "S3 Writer Tool"
|
|
description: str = "Writes content to a file in Amazon S3 given an S3 file path"
|
|
|
|
def _run(self, file_path: str, content: str) -> str:
|
|
try:
|
|
bucket_name, object_key = self._parse_s3_path(file_path)
|
|
|
|
s3 = boto3.client(
|
|
's3',
|
|
region_name=os.getenv('CREW_AWS_REGION', 'us-east-1'),
|
|
aws_access_key_id=os.getenv('CREW_AWS_ACCESS_KEY_ID'),
|
|
aws_secret_access_key=os.getenv('CREW_AWS_SEC_ACCESS_KEY')
|
|
)
|
|
|
|
s3.put_object(Bucket=bucket_name, Key=object_key, Body=content.encode('utf-8'))
|
|
return f"Successfully wrote content to {file_path}"
|
|
except ClientError as e:
|
|
return f"Error writing file to S3: {str(e)}"
|
|
```
|
|
|
|
## الخلاصة
|
|
|
|
توفر `S3WriterTool` طريقة مباشرة لكتابة المحتوى إلى ملفات في حاويات Amazon S3. من خلال تمكين الوكلاء من إنشاء وتحديث الملفات في S3، تسهّل سير العمل الذي يتطلب تخزين ملفات سحابي. هذه الأداة مفيدة بشكل خاص لحفظ البيانات وإدارة الإعدادات وتوليد التقارير وأي مهمة تتضمن تخزين المعلومات في تخزين AWS S3.
|