Weave Code
Client Laravel Package
alibabacloud/client
Alibaba Cloud SDK for PHP offering a unified client to call Alibaba Cloud APIs such as ECS, RDS, OSS, and SLB. Handles credentials, request signing, and retries, making it easy to integrate Alibaba Cloud services into Laravel or plain PHP apps. Note: largely superseded by newer Darabonba SDKs.
Alibaba Cloud Client for PHP - Use Alibaba Cloud in your PHP project
Frequently asked questions about Client
- How do I install alibabacloud/client in a Laravel application?
- Install it with Composer using a pinned version, then bind a configured client instance through your own service provider. There is no first-party Laravel package, so you own the configuration, credential loading, retry policy and logging. Keep the SDK calls behind an application-owned class such as CloudApiClient rather than injecting the vendor client into controllers or jobs.
- Does alibabacloud/client support Laravel 11 or Laravel 12?
- Not officially. Release 1.5.32 states support for PHP 5.5 through 8.1 only, and Laravel 11 and 12 require PHP 8.2 or newer. Installing it on those framework versions would need an unverified Composer constraint override. Treat the PHP 8.1 ceiling as a hard blocker until a dependency and runtime spike proves otherwise.
- Which PHP versions does alibabacloud/client support?
- The current 1.5.32 release advertises PHP 5.5 through 8.1. It does not cover PHP 8.2 or 8.3, which is what modern Laravel versions require. Pin your composer.json constraints accordingly or record an explicit, tested exception if you force a higher version.
- Is alibabacloud/client still maintained or should I use alibabacloud-php-sdk instead?
- This is the V1 OpenAPI SDK and Alibaba Cloud describes it as entering Basic Security Maintenance, with the vendor recommending the V2 SDK (alibabacloud-php-sdk, built on Darabonba) instead. Expect limited fixes and no feature roadmap on V1. For greenfield Laravel work, start with the V2 SDK and avoid this package entirely.
- How do I configure AccessKey, STS token or RAM role credentials with alibabacloud/client?
- The client accepts AccessKey pairs, STS tokens, RAM roles and credential chains through its configuration object. In Laravel, load these values from environment variables or a dedicated secrets manager and never commit them to source control. Rotate STS tokens through your own scheduled job and cache them, since the SDK does not manage token refresh for you.
- How do I call ECS, OSS or RDS APIs with the universal API caller?
- You pass the service endpoint, API version, action name and parameters to the client, and it handles RPC or ROA request signing and the HTTP transport automatically. That means no manual signature construction or raw cURL code. Wrap each call in a small internal method so business code never sees SDK request or response types.
- Can I configure proxies, timeouts and retries with alibabacloud/client?
- Yes, the transport layer allows proxies, connection and read timeouts, retry counts and pluggable HTTP handlers. Because there is no Laravel integration, you must wire these settings from config files yourself. Be careful with retries on non-idempotent API actions and add your own logging and backoff where needed.
- How do I test Laravel code that uses alibabacloud/client?
- There are no first-party testing helpers, so hide the SDK behind an internal interface and bind a fake implementation in your test container. Assert on the parameters your adapter sends rather than on HTTP traffic. Keep a small integration test suite that hits a sandbox account to catch signing or endpoint drift.
- What license does alibabacloud/client use?
- The GitHub repository reports a NOASSERTION license rather than a recognised SPDX identifier. That means the terms are ambiguous until legal reviews the actual LICENSE file and the Alibaba Cloud terms of service. Do not treat it as MIT or Apache-2.0 without that review.
- How do I migrate from alibabacloud/client to the V2 alibabacloud-php-sdk?
- Create an anti-corruption layer around your current V1 calls, map each action to an internal method, then implement a V2-backed adapter behind the same interface. Run both paths in parallel where you can, compare responses, and cut over per feature behind a flag. This keeps the migration out of business code and lets you track usage before removing the old package.
Weaver
How can I help you explore Laravel packages today?