@alienplatform/manager-api

Developer-friendly & type-safe Typescript SDK specifically catered to leverage @alienplatform/manager-api API.

[!IMPORTANT] This SDK is not yet ready for production use. To complete setup please follow the steps outlined in your workspace. Delete this section before > publishing to a package manager.

Summary

Alien Manager API: Control plane for Alien applications. Manages deployments, releases, commands, and telemetry.

Table of Contents

• @alienplatform/manager-api
  • SDK Installation
  • Requirements
  • SDK Example Usage
  • Authentication
  • Available Resources and Operations
  • Standalone functions
  • Retries
  • Error Handling
  • Custom HTTP Client
  • Debugging
• Development
  • Maturity
  • Contributions

SDK Installation

[!TIP] To finish publishing your SDK to npm and others you must run your first generation action.

The SDK can be installed with either npm, pnpm, bun or yarn package managers.

NPM

npm add <UNSET>

PNPM

pnpm add <UNSET>

Bun

bun add <UNSET>

Yarn

yarn add <UNSET>

[!NOTE] This package is published as an ES Module (ESM) only. For applications using CommonJS, use await import() to import and use this package.

Requirements

For supported JavaScript runtimes, please consult RUNTIMES.md.

SDK Example Usage

Example

import { AlienManager } from "@alienplatform/manager-api";

const alienManager = new AlienManager({
  serverURL: "https://api.example.com",
  bearer: process.env["ALIEN_MANAGER_BEARER"] ?? "",
});

async function run() {
  const result = await alienManager.health.health();

  console.log(result);
}

run();

Authentication

Per-Client Security Schemes

This SDK supports the following security scheme globally:

| Name | Type | Scheme | Environment Variable | | -------- | ------ | ------- | ---------------------- | | bearer | apiKey | API key | ALIEN_MANAGER_BEARER |

To authenticate with the API the bearer parameter must be set when initializing the SDK client instance. For example:

import { AlienManager } from "@alienplatform/manager-api";

const alienManager = new AlienManager({
  serverURL: "https://api.example.com",
  bearer: process.env["ALIEN_MANAGER_BEARER"] ?? "",
});

async function run() {
  const result = await alienManager.health.health();

  console.log(result);
}

run();

Available Resources and Operations

Commands

• createCommand - Create a new command
• getCommandStatus - Get command status
• getCommandPayload - Get command payload (params and response) from KV
• storeCommandPayload - Store command payload data (params and/or response) directly into KV.
• submitResponse - Submit response from deployment
• uploadComplete - Mark upload as complete

Credentials

• resolveCredentials

DeploymentGroups

• listDeploymentGroups
• createDeploymentGroup - Every handler in this file runs auth::require_auth(&state, &headers) and then threads &subject into the DeploymentStore calls — see the trait doc on [DeploymentStore] for the convention.
• getDeploymentGroup
• createDeploymentGroupToken

Deployments

• listDeployments
• createDeployment - Every handler in this file runs auth::require_auth(&state, &headers) and then threads &subject into the DeploymentStore calls. Embedders that proxy to an upstream API can use the subject's bearer_token for passthrough; single-tenant impls ignore it. See the trait doc on [DeploymentStore] for the full convention.
• getDeployment
• deleteDeployment
• getDeploymentInfo
• redeploy
• retryDeployment

Health

• health

Leases

• acquireLeases - Acquire leases for polling deployments
• releaseLease - Release a lease

Releases

• listReleases - GET /v1/releases — Inbound: workspace / project bearer (or authenticated user). Outbound: caller bearer (passthrough). Returns only releases the caller may read.
• createRelease
• getLatestRelease
• getRelease

StackImport

• stackImport - POST /v1/stack/import — Inbound: deployment-group bearer.

Sync

• initialize - POST /v1/initialize — Inbound: deployment-group bearer (typical), or workspace bearer for self-hosted operator workflows. New deployments are created via DeploymentStore::create_deployment(caller, …) so embedders that proxy to an upstream API write the row in the dg's workspace, not the manager's.
• agentSync - POST /v1/sync — Inbound: deployment bearer. The agent-driven sync path; caller: &Subject is threaded into the store so embedders see the agent's own scope.
• acquire - POST /v1/sync/acquire — Inbound: workspace / dg / deployment bearer. caller: &Subject is threaded into DeploymentStore::acquire so embedders can authorize against the inbound caller's scope.
• reconcile - POST /v1/sync/reconcile — Inbound: workspace / dg / deployment bearer. caller: &Subject is threaded into DeploymentStore::reconcile.
• release - POST /v1/sync/release — Inbound: workspace / dg / deployment bearer. caller: &Subject is threaded into DeploymentStore::release.

Whoami

• whoami

Standalone functions

All the methods listed above are available as standalone functions. These functions are ideal for use in applications running in the browser, serverless runtimes or other environments where application bundle size is a primary concern. When using a bundler to build your application, all unused functionality will be either excluded from the final bundle or tree-shaken away.

To read more about standalone functions, check FUNCTIONS.md.

• commandsCreateCommand - Create a new command
• commandsGetCommandPayload - Get command payload (params and response) from KV
• commandsGetCommandStatus - Get command status
• commandsStoreCommandPayload - Store command payload data (params and/or response) directly into KV.
• commandsSubmitResponse - Submit response from deployment
• commandsUploadComplete - Mark upload as complete
• credentialsResolveCredentials
• deploymentGroupsCreateDeploymentGroup - Every handler in this file runs auth::require_auth(&state, &headers) and then threads &subject into the DeploymentStore calls — see the trait doc on [DeploymentStore] for the convention.
• deploymentGroupsCreateDeploymentGroupToken
• deploymentGroupsGetDeploymentGroup
• deploymentGroupsListDeploymentGroups
• deploymentsCreateDeployment - Every handler in this file runs auth::require_auth(&state, &headers) and then threads &subject into the DeploymentStore calls. Embedders that proxy to an upstream API can use the subject's bearer_token for passthrough; single-tenant impls ignore it. See the trait doc on [DeploymentStore] for the full convention.
• deploymentsDeleteDeployment
• deploymentsGetDeployment
• deploymentsGetDeploymentInfo
• deploymentsListDeployments
• deploymentsRedeploy
• deploymentsRetryDeployment
• healthHealth
• leasesAcquireLeases - Acquire leases for polling deployments
• leasesReleaseLease - Release a lease
• releasesCreateRelease
• releasesGetLatestRelease
• releasesGetRelease
• releasesListReleases - GET /v1/releases — Inbound: workspace / project bearer (or authenticated user). Outbound: caller bearer (passthrough). Returns only releases the caller may read.
• stackImportStackImport - POST /v1/stack/import — Inbound: deployment-group bearer.
• syncAcquire - POST /v1/sync/acquire — Inbound: workspace / dg / deployment bearer. caller: &Subject is threaded into DeploymentStore::acquire so embedders can authorize against the inbound caller's scope.
• syncAgentSync - POST /v1/sync — Inbound: deployment bearer. The agent-driven sync path; caller: &Subject is threaded into the store so embedders see the agent's own scope.
• syncInitialize - POST /v1/initialize — Inbound: deployment-group bearer (typical), or workspace bearer for self-hosted operator workflows. New deployments are created via DeploymentStore::create_deployment(caller, …) so embedders that proxy to an upstream API write the row in the dg's workspace, not the manager's.
• syncReconcile - POST /v1/sync/reconcile — Inbound: workspace / dg / deployment bearer. caller: &Subject is threaded into DeploymentStore::reconcile.
• syncRelease - POST /v1/sync/release — Inbound: workspace / dg / deployment bearer. caller: &Subject is threaded into DeploymentStore::release.
• whoamiWhoami

Retries

Some of the endpoints in this SDK support retries. If you use the SDK without any configuration, it will fall back to the default retry strategy provided by the API. However, the default retry strategy can be overridden on a per-operation basis, or across the entire SDK.

To change the default retry strategy for a single API call, simply provide a retryConfig object to the call:

import { AlienManager } from "@alienplatform/manager-api";

const alienManager = new AlienManager({
  serverURL: "https://api.example.com",
  bearer: process.env["ALIEN_MANAGER_BEARER"] ?? "",
});

async function run() {
  const result = await alienManager.health.health({
    retries: {
      strategy: "backoff",
      backoff: {
        initialInterval: 1,
        maxInterval: 50,
        exponent: 1.1,
        maxElapsedTime: 100,
      },
      retryConnectionErrors: false,
    },
  });

  console.log(result);
}

run();

If you'd like to override the default retry strategy for all operations that support retries, you can provide a retryConfig at SDK initialization:

import { AlienManager } from "@alienplatform/manager-api";

const alienManager = new AlienManager({
  serverURL: "https://api.example.com",
  retryConfig: {
    strategy: "backoff",
    backoff: {
      initialInterval: 1,
      maxInterval: 50,
      exponent: 1.1,
      maxElapsedTime: 100,
    },
    retryConnectionErrors: false,
  },
  bearer: process.env["ALIEN_MANAGER_BEARER"] ?? "",
});

async function run() {
  const result = await alienManager.health.health();

  console.log(result);
}

run();

Error Handling

AlienManagerError is the base class for all HTTP error responses. It has the following properties:

| Property | Type | Description | | ------------------- | ---------- | --------------------------------------------------------------------------------------- | | error.message | string | Error message | | error.statusCode | number | HTTP response status code eg 404 | | error.headers | Headers | HTTP response headers | | error.body | string | HTTP body. Can be empty string if no body is returned. | | error.rawResponse | Response | Raw HTTP response | | error.data$ | | Optional. Some errors may contain structured data. See Error Classes. |

Example

import { AlienManager } from "@alienplatform/manager-api";
import * as errors from "@alienplatform/manager-api/models/errors";

const alienManager = new AlienManager({
  serverURL: "https://api.example.com",
  bearer: process.env["ALIEN_MANAGER_BEARER"] ?? "",
});

async function run() {
  try {
    const result = await alienManager.commands.createCommand({
      command: "<value>",
      deploymentId: "<id>",
      params: {
        mode: "storage",
      },
    });

    console.log(result);
  } catch (error) {
    // The base class for HTTP error responses
    if (error instanceof errors.AlienManagerError) {
      console.log(error.message);
      console.log(error.statusCode);
      console.log(error.body);
      console.log(error.headers);

      // Depending on the method different errors may be thrown
      if (error instanceof errors.ErrorResponse) {
        console.log(error.data$.code); // string
        console.log(error.data$.details); // string
        console.log(error.data$.message); // string
      }
    }
  }
}

run();

Error Classes

Primary error:

• AlienManagerError: The base class for HTTP error responses.

Network errors:

• ConnectionError: HTTP client was unable to make a request to a server.
• RequestTimeoutError: HTTP request timed out due to an AbortSignal signal.
• RequestAbortedError: HTTP request was aborted by the client.
• InvalidRequestError: Any input used to create a request is invalid.
• UnexpectedClientError: Unrecognised or unexpected error.

Inherit from AlienManagerError:

• ErrorResponse: Error response wrapper for API endpoints. Applicable to 8 of 32 methods.*
• ResponseValidationError: Type mismatch between the data returned from the server and the structure expected by the SDK. See error.rawValue for the raw value and error.pretty() for a nicely formatted multi-line string.

* Check the method documentation to see if the error is applicable.

Custom HTTP Client

The TypeScript SDK makes API calls using an HTTPClient that wraps the native Fetch API. This client is a thin wrapper around fetch and provides the ability to attach hooks around the request lifecycle that can be used to modify the request or handle errors and response.

The HTTPClient constructor takes an optional fetcher argument that can be used to integrate a third-party HTTP client or when writing tests to mock out the HTTP client and feed in fixtures.

The following example shows how to use the "beforeRequest" hook to to add a custom header and a timeout to requests and how to use the "requestError" hook to log errors:

import { AlienManager } from "@alienplatform/manager-api";
import { HTTPClient } from "@alienplatform/manager-api/lib/http";

const httpClient = new HTTPClient({
  // fetcher takes a function that has the same signature as native `fetch`.
  fetcher: (request) => {
    return fetch(request);
  }
});

httpClient.addHook("beforeRequest", (request) => {
  const nextRequest = new Request(request, {
    signal: request.signal || AbortSignal.timeout(5000)
  });

  nextRequest.headers.set("x-custom-header", "custom value");

  return nextRequest;
});

httpClient.addHook("requestError", (error, request) => {
  console.group("Request Error");
  console.log("Reason:", `${error}`);
  console.log("Endpoint:", `${request.method} ${request.url}`);
  console.groupEnd();
});

const sdk = new AlienManager({ httpClient: httpClient });

Debugging

You can setup your SDK to emit debug logs for SDK requests and responses.

You can pass a logger that matches console's interface as an SDK option.

[!WARNING] Beware that debug logging will reveal secrets, like API tokens in headers, in log messages printed to a console or files. It's recommended to use this feature only during local development and not in production.

import { AlienManager } from "@alienplatform/manager-api";

const sdk = new AlienManager({ debugLogger: console });

You can also enable a default debug logger by setting an environment variable ALIEN_MANAGER_DEBUG to true.

Development

Maturity

This SDK is in beta, and there may be breaking changes between versions without a major version update. Therefore, we recommend pinning usage to a specific package version. This way, you can install the same version each time without breaking changes unless you are intentionally looking for the latest version.

Contributions

While we value open-source contributions to this SDK, this library is generated programmatically. Any manual changes added to internal files will be overwritten on the next generation. We look forward to hearing your feedback. Feel free to open a PR or an issue with a proof of concept and we'll do our best to include it in a future release.

SDK Created by Speakeasy