steadlake

Developer-friendly & type-safe Typescript SDK specifically catered to leverage Steadlake API.

Summary

Steadlake API: Official TypeScript API client for the Steadlake platform.

Table of Contents

• steadlake
  • SDK Installation
  • Requirements
  • SDK Example Usage
  • Authentication
  • Available Resources and Operations
  • Standalone functions
  • Retries
  • Error Handling
  • Server Selection
  • 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 { Steadlake } from "@steadlake/core";

const steadlake = new Steadlake({
  bearerAuth: process.env["STEADLAKE_BEARER_AUTH"] ?? "",
});

async function run() {
  const result = await steadlake.triggers.register({
    projectId: "<id>",
    triggers: [
      {
        handler: "<value>",
        name: "<value>",
      },
    ],
  });

  console.log(result);
}

run();

Authentication

Per-Client Security Schemes

This SDK supports the following security scheme globally:

| Name | Type | Scheme | Environment Variable | | ------------ | ---- | ----------- | ----------------------- | | bearerAuth | http | HTTP Bearer | STEADLAKE_BEARER_AUTH |

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

import { Steadlake } from "@steadlake/core";

const steadlake = new Steadlake({
  bearerAuth: process.env["STEADLAKE_BEARER_AUTH"] ?? "",
});

async function run() {
  const result = await steadlake.triggers.register({
    projectId: "<id>",
    triggers: [
      {
        handler: "<value>",
        name: "<value>",
      },
    ],
  });

  console.log(result);
}

run();

Available Resources and Operations

Events

• publishEvent - Publish an event: fans out to subscribed triggers and resumes waiters

Runs

• create - Create a new run with optional configuration
• status - Get current status of a run
• get - Get detailed run information
• cancel - Cancel a running execution
• replay - Replay a run with the same payload
• sendEvent - Deliver an event to a run waiting via waitForEvent
• approve - Resolve an approval gate on a suspended run

Triggers

• register - Bulk register or update triggers for a project
• getSigningSecret - Fetch the project's auto-provisioned signing secret (used by the SDK to verify dispatch signatures)
• syncCron - Sync cron trigger next fire time from pattern

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.

• eventsPublishEvent - Publish an event: fans out to subscribed triggers and resumes waiters
• runsApprove - Resolve an approval gate on a suspended run
• runsCancel - Cancel a running execution
• runsCreate - Create a new run with optional configuration
• runsGet - Get detailed run information
• runsReplay - Replay a run with the same payload
• runsSendEvent - Deliver an event to a run waiting via waitForEvent
• runsStatus - Get current status of a run
• triggersGetSigningSecret - Fetch the project's auto-provisioned signing secret (used by the SDK to verify dispatch signatures)
• triggersRegister - Bulk register or update triggers for a project
• triggersSyncCron - Sync cron trigger next fire time from pattern

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 { Steadlake } from "@steadlake/core";

const steadlake = new Steadlake({
  bearerAuth: process.env["STEADLAKE_BEARER_AUTH"] ?? "",
});

async function run() {
  const result = await steadlake.triggers.register({
    projectId: "<id>",
    triggers: [
      {
        handler: "<value>",
        name: "<value>",
      },
    ],
  }, {
    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 { Steadlake } from "@steadlake/core";

const steadlake = new Steadlake({
  retryConfig: {
    strategy: "backoff",
    backoff: {
      initialInterval: 1,
      maxInterval: 50,
      exponent: 1.1,
      maxElapsedTime: 100,
    },
    retryConnectionErrors: false,
  },
  bearerAuth: process.env["STEADLAKE_BEARER_AUTH"] ?? "",
});

async function run() {
  const result = await steadlake.triggers.register({
    projectId: "<id>",
    triggers: [
      {
        handler: "<value>",
        name: "<value>",
      },
    ],
  });

  console.log(result);
}

run();

Error Handling

SteadlakeError 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 |

Example

import { Steadlake } from "@steadlake/core";
import * as errors from "@steadlake/core/models/errors";

const steadlake = new Steadlake({
  bearerAuth: process.env["STEADLAKE_BEARER_AUTH"] ?? "",
});

async function run() {
  try {
    const result = await steadlake.triggers.register({
      projectId: "<id>",
      triggers: [
        {
          handler: "<value>",
          name: "<value>",
        },
      ],
    });

    console.log(result);
  } catch (error) {
    if (error instanceof errors.SteadlakeError) {
      console.log(error.message);
      console.log(error.statusCode);
      console.log(error.body);
      console.log(error.headers);
    }
  }
}

run();

Error Classes

Primary error:

• SteadlakeError: 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 SteadlakeError:

• 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.

Server Selection

Override Server URL Per-Client

The default server can be overridden globally by passing a URL to the serverURL: string optional parameter when initializing the SDK client instance. For example:

import { Steadlake } from "@steadlake/core";

const steadlake = new Steadlake({
  serverURL: "https://api.steadlake.com",
  bearerAuth: process.env["STEADLAKE_BEARER_AUTH"] ?? "",
});

async function run() {
  const result = await steadlake.triggers.register({
    projectId: "<id>",
    triggers: [
      {
        handler: "<value>",
        name: "<value>",
      },
    ],
  });

  console.log(result);
}

run();

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:

• route requests through a proxy server using undici's ProxyAgent
• use the "beforeRequest" hook to add a custom header and a timeout to requests
• use the "requestError" hook to log errors

import { Steadlake } from "@steadlake/core";
import { ProxyAgent } from "undici";
import { HTTPClient } from "@steadlake/core/lib/http";

const dispatcher = new ProxyAgent("http://proxy.example.com:8080");

const httpClient = new HTTPClient({
  // 'fetcher' takes a function that has the same signature as native 'fetch'.
  fetcher: (input, init) =>
    // 'dispatcher' is specific to undici and not part of the standard Fetch API.
    fetch(input, { ...init, dispatcher } as RequestInit),
});

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 Steadlake({ 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 { Steadlake } from "@steadlake/core";

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

You can also enable a default debug logger by setting an environment variable STEADLAKE_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