Manage Deployments with the Columnar Management API

The Management API v4.0 uses semantic versioning. The full version number consists of three parts: major.minor.patch.

An update to the Management API may be a non-versioned bug fix, a patch update, a minor update, or a major update. When a non-versioned bug fix is released, the version number is not updated. When a patch update, a minor update, or a major update is released, the version number is updated also.

With few exceptions, new versions of Management API are backward compatible, minimizing the impact to existing deployments. In most cases, you are not required to update your existing infrastructure when a new version of the Management API is released. Features added in a new version of the Management API will not break existing deployments.

Exceptions to backward compatibility are as follows:

The Management API v4.0 is the initial release of the Capella Columnar Management API. The version numbering of the Capella Columnar Management API is aligned with the version numbering of the Capella operational Management API.

The Management API v4.0 uses API keys for authentication and authorization. Please note that you need new API keys to access endpoints exposed by the Management API v4.0.

API keys are associated with Couchbase Capella roles and permissions. An API key must have the appropriate Capella roles to access an endpoint. The Management API reference guide lists the roles that are needed for each endpoint.

Every API key is associated with an allowed IP Address list, which can be configured during API key creation. Every API key has an expiration date.

To authenticate a Management API call, the API key must be passed as a Bearer token using the HTTP Authorization header.

To support concurrent requests, PUT requests support optimistic concurrency control, using If-Match headers in combination with HTTP ETags (entity tags). Exceptions are noted in the endpoint descriptions. A typical pattern is to do a GET request on a specified resource, which returns an ETag value. You can then include the ETag value in a PUT request to update the resource.

PUT requests ignore all fields in the body of the request that are not required. Required fields for each PUT request are specified in the Management API reference guide.

All requests to the Management API are audited. All endpoints support Audit fields for audit purposes, except where noted in the Management API reference guide.

Lists are paginated.