volcengine-storage-tos-test

What This Skill Does

The volcengine-storage-tos-test skill provides a robust framework for validating Volcengine Object Storage (TOS) connectivity and configuration. As a technical testing utility, it allows developers and DevOps engineers to perform critical smoke tests to ensure their environment is properly authenticated and capable of basic storage operations. The skill supports two primary interfaces: the custom tos_manage.py Python script for automated programmatic validation and the official tosutil command-line tool for production-standard verification. By executing these tests, users can confirm their AK/SK credentials, region settings, and endpoint reachability before deploying resource-heavy applications into the TOS ecosystem.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/day253/day253-volcengine-storage-tos-test

Ensure that you have the required Python dependencies installed by running pip install tos. Before execution, verify that your environment variables (TOS_ACCESS_KEY, TOS_SECRET_KEY, TOS_ENDPOINT) are correctly exported in your .env file or shell session to enable seamless interaction with the Volcengine storage services.

Use Cases

• Environment Validation: Quickly verify if a new developer machine or a CI/CD pipeline agent has correct access rights to the company's storage infrastructure.
• Troubleshooting Connection Issues: Isolate failures between authentication errors (403), misconfigured regions, or network endpoint accessibility problems.
• Smoke Testing: Perform a pre-flight check after updating IAM roles or bucket policies to ensure storage operations like reading, writing, and listing are still functional.
• Automation Testing: Integrate into automated workflows to generate pre-signed URLs for time-limited, secure access to files.

Example Prompts

• "OpenClaw, run the TOS smoke test suite using the tos_manage.py script to verify I can list buckets and upload a test file."
• "I'm getting a 403 error on my Volcengine storage; please run the diagnostics provided by the tos-test skill to pinpoint if my credentials or permissions are the issue."
• "Generate a pre-signed URL for the test file I just uploaded to my storage bucket and show me the output."

Tips & Limitations

• Permissions: Ensure your IAM user has at least tos:ListBucket, tos:PutObject, and tos:GetObject permissions. Over-privileged keys are a security risk; follow the principle of least privilege.
• Cleanup: Always use the cleanup functionality provided in the scripts. Leaving test files in production buckets can incur unnecessary costs and clutter your data lake.
• Endpoints: Double-check that your endpoint follows the standard format tos-{region}.volces.com. A common failure point is mixing up regions.
• Data Integrity: While the script performs a diff check, verify your local disk has sufficient space when performing large file downloads during your testing cycles.