augusl/zenlayercloud-laravel-sdk
Composer 安装命令:
composer require augusl/zenlayercloud-laravel-sdk
包简介
Laravel SDK for Zenlayer Cloud — Virtual Machine (VM) and Elastic Compute (ZEC) services.
README 文档
README
中文文档 · English
Unofficial, community-maintained SDK. This package is not affiliated with or endorsed by Zenlayer Inc. It is built and maintained by community contributors against the public Zenlayer Cloud OpenAPI documentation. Bug reports and feature requests belong here; Zenlayer Cloud product questions belong on the official documentation site.
A first-class Laravel package for talking to Zenlayer Cloud
OpenAPI services. Designed to feel native — service providers, facades,
configurable connections, the standard Illuminate\Http\Client for transport,
and Http::fake() support out of the box.
The v0.1.x line covers the Compute product group:
- Virtual Machine (VM) — API version
2026-04-01, 62 actions. - Elastic Compute (ZEC) — API version
2025-09-01, 214 actions.
Every Zenlayer Cloud Action is exposed as a typed PHP method backed by typed Request and Response model classes, so IDEs autocomplete the entire surface area.
Requirements
| Component | Version |
|---|---|
| PHP | ^8.2 |
| Laravel | 11.x · 12.x · 13.x |
ext-json |
enabled (default) |
ext-hash |
enabled (default) |
Installation
composer require augusl/zenlayercloud-laravel-sdk
Publish the configuration file:
php artisan vendor:publish --tag=zenlayercloud-config
Set credentials in your .env. Either an AccessKey pair (HMAC signing):
ZENLAYER_SECRET_KEY_ID=AKID-your-key-id ZENLAYER_SECRET_KEY_PASSWORD=your-secret-key-password
…or a personal access token (Bearer auth — takes precedence when set, generate one at https://console.zenlayer.com/accessToken):
ZENLAYER_TOKEN=your-personal-access-token
The package supports Laravel's auto-discovery — the service provider and
the ZenlayerCloud facade are registered for you.
Quick start
Resolve clients
There are three equivalent ways to obtain a client:
use ZenlayerCloud\Laravel\Facades\ZenlayerCloud; use ZenlayerCloud\Laravel\Vm\V20260401\VmClient; use ZenlayerCloud\Laravel\Zec\V20250901\ZecClient; // 1. Facade $vm = ZenlayerCloud::vm(); // 2. Container resolution (defaults to the 'default' connection) $vm = app(VmClient::class); // 3. Constructor injection public function __construct(private VmClient $vm) {}
List availability zones
use ZenlayerCloud\Laravel\Facades\ZenlayerCloud; use ZenlayerCloud\Laravel\Vm\V20260401\Models\DescribeZonesRequest; $response = ZenlayerCloud::vm()->DescribeZones(new DescribeZonesRequest()); foreach ($response->response->zoneSet as $zone) { echo $zone->zoneId, ' ', $zone->zoneName, PHP_EOL; }
Create a virtual machine
use ZenlayerCloud\Laravel\Facades\ZenlayerCloud; use ZenlayerCloud\Laravel\Vm\V20260401\Models\ChargePrepaid; use ZenlayerCloud\Laravel\Vm\V20260401\Models\CreateInstancesRequest; use ZenlayerCloud\Laravel\Vm\V20260401\Models\SystemDisk; $req = new CreateInstancesRequest(); $req->zoneId = 'SEL-A'; $req->imageId = 'IMG-xxxx'; $req->instanceType = 'S8I'; $req->instanceCount = 1; $req->instanceChargeType = 'PREPAID'; $req->instanceChargePrepaid = new ChargePrepaid(); $req->instanceChargePrepaid->period = 12; $req->systemDisk = new SystemDisk(); $req->systemDisk->diskSize = 50; $resp = ZenlayerCloud::vm()->CreateInstances($req); logger()->info('Order placed', [ 'order' => $resp->response->orderNumber, 'instances' => $resp->response->instanceIdSet ?? [], ]);
Elastic Compute (ZEC)
use ZenlayerCloud\Laravel\Facades\ZenlayerCloud; use ZenlayerCloud\Laravel\Zec\V20250901\Models\DescribeVpcsRequest; $resp = ZenlayerCloud::zec()->DescribeVpcs(new DescribeVpcsRequest()); foreach ($resp->response->dataSet as $vpc) { echo $vpc->vpcId, PHP_EOL; }
Error handling
Every transport- and API-level failure surfaces as one typed exception:
use ZenlayerCloud\Laravel\Common\Exception\ZenlayerCloudSdkException; try { $resp = ZenlayerCloud::vm()->DescribeInstances(new DescribeInstancesRequest()); } catch (ZenlayerCloudSdkException $e) { report($e); abort(502, sprintf( 'Zenlayer error %s (request %s): %s', $e->errorCode, $e->requestId ?? '-', $e->getMessage(), )); }
The exception exposes $e->errorCode (e.g. INVALID_PARAMETER,
NETWORK_ERROR, CREDENTIAL_VALUE_MISSING, CONFIG_INVALID) and
$e->requestId for log correlation. Transport-level failures (DNS,
connection refused, TLS, timeout) are wrapped with code NETWORK_ERROR;
you never need to catch Laravel's ConnectionException separately.
When retry is enabled, only network-level failures are retried —
HTTP error responses are never retried, so non-idempotent Actions such as
CreateInstances cannot run twice.
Configuration
The published config/zenlayercloud.php file follows Laravel's "connection"
convention used by the database, cache, and mail components:
return [ 'default' => env('ZENLAYER_CONNECTION', 'default'), 'connections' => [ 'default' => [ 'secret_key_id' => env('ZENLAYER_SECRET_KEY_ID'), 'secret_key_password' => env('ZENLAYER_SECRET_KEY_PASSWORD'), 'token' => env('ZENLAYER_TOKEN'), // Bearer auth; wins over the key pair when set 'endpoint' => env('ZENLAYER_ENDPOINT', 'console.zenlayer.com'), 'scheme' => env('ZENLAYER_SCHEME', 'https'), 'timeout' => (int) env('ZENLAYER_TIMEOUT', 60), 'retry' => (bool) env('ZENLAYER_RETRY', false), 'retry_max' => (int) env('ZENLAYER_RETRY_MAX', 3), 'debug' => (bool) env('ZENLAYER_DEBUG', false), 'proxy' => env('ZENLAYER_PROXY'), 'verify' => env('ZENLAYER_VERIFY', true), // true | false | CA bundle path 'request_client' => env('ZENLAYER_REQUEST_CLIENT'), ], 'staging' => [ // a second account, used per-call: ZenlayerCloud::vm('staging') ], ], ];
Switch between connections with the optional argument to the manager:
ZenlayerCloud::vm(); // 'default' ZenlayerCloud::vm('staging'); // named connection ZenlayerCloud::zec('production'); // any name from the 'connections' map
Testing the SDK in your app
The transport layer is built on Illuminate\Http\Client, so Laravel's
built-in Http::fake() is the only thing you need to mock the API:
use Illuminate\Support\Facades\Http; use ZenlayerCloud\Laravel\Facades\ZenlayerCloud; use ZenlayerCloud\Laravel\Vm\V20260401\Models\DescribeZonesRequest; Http::fake([ 'console.zenlayer.com/*' => Http::response([ 'requestId' => 'r-1', 'response' => [ 'requestId' => 'r-1', 'zoneSet' => [['zoneId' => 'SEL-A', 'zoneName' => 'Seoul A']], ], ], 200), ]); $resp = ZenlayerCloud::vm()->DescribeZones(new DescribeZonesRequest()); self::assertSame('SEL-A', $resp->response->zoneSet[0]->zoneId); Http::assertSent(fn ($r) => $r->header('x-zc-action')[0] === 'DescribeZones');
Conventions
- Method names follow the upstream Action names (PascalCase) — e.g.
DescribeInstances,CreateInstances,ModifyInstancesAttribute. This keeps copy-paste from the Zenlayer Cloud API reference unambiguous. The shippedpint.jsondoes not enforce PSR-12 camelCase on those generated client methods. - Models are plain data objects — public typed nullable properties for every field on the Action's schema. Null fields are omitted from the JSON body sent over the wire.
- Responses come in wrappers — every Action returns a
XxxResponsewhoserequestIdlives at the top level and whose payload lives underresponse. Access fields via$resp->response->....
Local development
# Install dev dependencies composer install # Run the test suite (Orchestra Testbench + PHPUnit) composer test # Run code-style checks composer lint composer lint:fix # Run static analysis composer analyse # Regenerate the client + model classes from the upstream schema ZENLAYER_SCHEMA_SRC=/path/to/upstream/schema composer codegen
See CONTRIBUTING.md for the full contributor workflow.
Roadmap
The first release line (v0.1.x) covers VM + ZEC. Other Zenlayer Cloud
product groups (BMC, CCS, Traffic, ZDNS, ZGA, ZLB, ZLS, ZOS, ZRM, etc.) are
deferred to subsequent minor versions; contributions are welcome.
Security
Found a vulnerability? Please follow the responsible-disclosure process described in SECURITY.md — do not file a public issue.
License
Apache-2.0 — see LICENSE.
Disclaimer
This is an unofficial, community-maintained Laravel SDK. It is provided as-is, with no affiliation with, sponsorship from, or endorsement by Zenlayer Inc. or any of its subsidiaries. "Zenlayer" and "Zenlayer Cloud" are trademarks of their respective owners; this project uses those names solely to describe the upstream service it integrates with.
augusl/zenlayercloud-laravel-sdk 适用场景与选型建议
augusl/zenlayercloud-laravel-sdk 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 1 次下载、GitHub Stars 达 0, 最近一次更新时间为 2026 年 05 月 13 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「sdk」 「cloud」 「laravel」 「vm」 「zec」 「zenlayer」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 augusl/zenlayercloud-laravel-sdk 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 augusl/zenlayercloud-laravel-sdk 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 augusl/zenlayercloud-laravel-sdk 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
A SDK for working with B2 cloud storage.
Small library to access Microsoft Windows Azure Blob Storage with a Service or a StreamWrapper.
UCloud Resource (Cloud) Storage SDK for PHP
The flysystem adapter for yandex disk rest api.
A sleek PHP wrapper around rclone with Laravel-style fluent API syntax
非官方云小票机SDK,支持飞鹅云,芯烨云,易联云,快递100,映美云,中午云,佳博云,优声云,365智能云打印等
统计信息
- 总下载量: 1
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 0
- 点击次数: 46
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: Apache-2.0
- 更新时间: 2026-05-13