Admin Panel API Changelog 2.4.2
Previous Release: 2.4.1 · New Release: 2.4.2
Audience: external integrators and service-to-service consumers of the Admin Panel API — service accounts, provisioning automation, and integration tooling.
This document covers the Admin Panel API changes between the 2.4.1 and 2.4.2 releases.
1. Summary — What Actually Affects You
There are no breaking changes. No endpoint was removed or renamed, no request or response field was removed or retyped, and no behaviour changed for an existing call. Upgrading from 2.4.1 to 2.4.2 requires no changes to an existing Admin Panel integration.
This release is additive: one new endpoint and one new response field.
Metric | Count |
|---|---|
New endpoints | 1 |
Removed endpoints | 0 |
Breaking changes | 0 |
Deprecations | 0 |
New response fields | 1 |
2. New Endpoints
Method | Path | Purpose |
|---|---|---|
GET |
| Retrieve the SSH access credentials for a bare-metal subscription. |
Response fields: subscription_id, ssh_host, ssh_port, ssh_user, ssh_password.
This endpoint returns access credentials. Treat the response as secret: do not log it, cache it in shared storage, or forward it to clients that do not need it.
3. New Response Field: shared_storage_capable
GPU pool responses now carry a shared_storage_capable boolean, indicating whether the pool's region can back shared storage. It is reported independently of rootfs_persistence_capable; do not infer one from the other.
The field appears on:
GET /api/gpuaas/pools/allGET /api/gpuaas/{gpuaas_id}/pool/listPOST /api/gpuaas/pool/createDELETE /api/gpuaas/pool/{pool_id}/delete
The change is additive. Clients that ignore unknown fields need no action.
4. Removed or Deprecated
Nothing was removed or deprecated in this release.
5. Specification Coverage for This Release
The published specification for this release does not yet include the endpoint described in Section 2 or the field described in Section 3. An updated specification will follow.
Until it is published, please note:
Use this changelog as the reference for the 2.4.2 Admin Panel API surface. A specification comparison will understate this release.
An SDK generated from the current specification will not include the new endpoint or the new field. Call the endpoint directly, or extend your model manually, until the updated specification is available.
Clients configured to reject unknown response fields should be checked against Section 3 before upgrading.
6. Migration Checklist
Confirm your client tolerates unknown response fields, or add shared_storage_capable to your GPU pool model (Section 3).
Use this changelog rather than a specification comparison to scope the upgrade (Section 5).
Optionally adopt the bare-metal subscription credentials endpoint, handling the response as secret material (Section 2).