truefoundry-sdk
v0.1.18
Published
[](https://buildwithfern.com?utm_source=github&utm_medium=github&utm_campaign=readme&utm_source=https%3A%2F%2Fgithub.com%2Ftruefoundry%2Ftruefoundry-typescript-sdk) [
Readme
Truefoundry TypeScript Library
This library provides convenient access to the TrueFoundry API.
[!tip] You can ask questions about this SDK using DeepWiki
Table of Contents
- Installation
- Reference
- Usage
- Request and Response Types
- Exception Handling
- Pagination
- Advanced
- Contributing
Installation
npm i -s truefoundry-sdkReference
A full reference for this library is available here.
Usage
Instantiate and use the client with the following:
import { TrueFoundryClient } from "truefoundry-sdk";
const client = new TrueFoundryClient({ environment: "YOUR_BASE_URL", apiKey: "YOUR_API_KEY" });
const pageableResponse = await client.applications.list({
limit: 10,
offset: 0,
applicationId: "applicationId",
workspaceId: "workspaceId",
applicationName: "applicationName",
fqn: "fqn",
workspaceFqn: "workspaceFqn",
applicationType: "applicationType",
nameSearchQuery: "nameSearchQuery",
environmentId: "environmentId",
clusterId: "clusterId",
applicationSetId: "applicationSetId",
paused: true,
deviceTypeFilter: "cpu",
lastDeployedBySubjects: "lastDeployedBySubjects",
lifecycleStage: "active",
isRecommendationPresentAndVisible: true
});
for await (const item of pageableResponse) {
console.log(item);
}
// Or you can manually iterate page-by-page
let page = await client.applications.list({
limit: 10,
offset: 0,
applicationId: "applicationId",
workspaceId: "workspaceId",
applicationName: "applicationName",
fqn: "fqn",
workspaceFqn: "workspaceFqn",
applicationType: "applicationType",
nameSearchQuery: "nameSearchQuery",
environmentId: "environmentId",
clusterId: "clusterId",
applicationSetId: "applicationSetId",
paused: true,
deviceTypeFilter: "cpu",
lastDeployedBySubjects: "lastDeployedBySubjects",
lifecycleStage: "active",
isRecommendationPresentAndVisible: true
});
while (page.hasNextPage()) {
page = page.getNextPage();
}
// You can also access the underlying response
const response = page.response;Request and Response Types
The SDK exports all request and response types as TypeScript interfaces. Simply import them with the following namespace:
import { TrueFoundry } from "truefoundry-sdk";
const request: TrueFoundry.InternalGetIdFromFqnRequest = {
...
};Exception Handling
When the API returns a non-success status code (4xx or 5xx response), a subclass of the following error will be thrown.
import { TrueFoundryError } from "truefoundry-sdk";
try {
await client.applications.list(...);
} catch (err) {
if (err instanceof TrueFoundryError) {
console.log(err.statusCode);
console.log(err.message);
console.log(err.body);
console.log(err.rawResponse);
}
}Pagination
List endpoints are paginated. The SDK provides an iterator so that you can simply loop over the items:
import { TrueFoundryClient } from "truefoundry-sdk";
const client = new TrueFoundryClient({ environment: "YOUR_BASE_URL", apiKey: "YOUR_API_KEY" });
const pageableResponse = await client.users.list({
limit: 10,
offset: 0,
query: "query",
showInvalidUsers: true,
includeVirtualAccounts: "includeVirtualAccounts"
});
for await (const item of pageableResponse) {
console.log(item);
}
// Or you can manually iterate page-by-page
let page = await client.users.list({
limit: 10,
offset: 0,
query: "query",
showInvalidUsers: true,
includeVirtualAccounts: "includeVirtualAccounts"
});
while (page.hasNextPage()) {
page = page.getNextPage();
}
// You can also access the underlying response
const response = page.response;Advanced
Additional Headers
If you would like to send additional headers as part of the request, use the headers request option.
import { TrueFoundryClient } from "truefoundry-sdk";
const client = new TrueFoundryClient({
...
headers: {
'X-Custom-Header': 'custom value'
}
});
const response = await client.applications.list(..., {
headers: {
'X-Custom-Header': 'custom value'
}
});Additional Query String Parameters
If you would like to send additional query string parameters as part of the request, use the queryParams request option.
const response = await client.applications.list(..., {
queryParams: {
'customQueryParamKey': 'custom query param value'
}
});Retries
The SDK is instrumented with automatic retries with exponential backoff. A request will be retried as long as the request is deemed retryable and the number of retry attempts has not grown larger than the configured retry limit (default: 2).
A request is deemed retryable when any of the following HTTP status codes is returned:
Use the maxRetries request option to configure this behavior.
const response = await client.applications.list(..., {
maxRetries: 0 // override maxRetries at the request level
});Timeouts
The SDK defaults to a 60 second timeout. Use the timeoutInSeconds option to configure this behavior.
const response = await client.applications.list(..., {
timeoutInSeconds: 30 // override timeout to 30s
});Aborting Requests
The SDK allows users to abort requests at any point by passing in an abort signal.
const controller = new AbortController();
const response = await client.applications.list(..., {
abortSignal: controller.signal
});
controller.abort(); // aborts the requestAccess Raw Response Data
The SDK provides access to raw response data, including headers, through the .withRawResponse() method.
The .withRawResponse() method returns a promise that results to an object with a data and a rawResponse property.
const { data, rawResponse } = await client.applications.list(...).withRawResponse();
console.log(data);
console.log(rawResponse.headers['X-My-Header']);Logging
The SDK supports logging. You can configure the logger by passing in a logging object to the client options.
import { TrueFoundryClient, logging } from "truefoundry-sdk";
const client = new TrueFoundryClient({
...
logging: {
level: logging.LogLevel.Debug, // defaults to logging.LogLevel.Info
logger: new logging.ConsoleLogger(), // defaults to ConsoleLogger
silent: false, // defaults to true, set to false to enable logging
}
});The logging object can have the following properties:
level: The log level to use. Defaults tologging.LogLevel.Info.logger: The logger to use. Defaults to alogging.ConsoleLogger.silent: Whether to silence the logger. Defaults totrue.
The level property can be one of the following values:
logging.LogLevel.Debuglogging.LogLevel.Infologging.LogLevel.Warnlogging.LogLevel.Error
To provide a custom logger, you can pass in an object that implements the logging.ILogger interface.
Here's an example using the popular winston logging library.
import winston from 'winston';
const winstonLogger = winston.createLogger({...});
const logger: logging.ILogger = {
debug: (msg, ...args) => winstonLogger.debug(msg, ...args),
info: (msg, ...args) => winstonLogger.info(msg, ...args),
warn: (msg, ...args) => winstonLogger.warn(msg, ...args),
error: (msg, ...args) => winstonLogger.error(msg, ...args),
};Here's an example using the popular pino logging library.
import pino from 'pino';
const pinoLogger = pino({...});
const logger: logging.ILogger = {
debug: (msg, ...args) => pinoLogger.debug(args, msg),
info: (msg, ...args) => pinoLogger.info(args, msg),
warn: (msg, ...args) => pinoLogger.warn(args, msg),
error: (msg, ...args) => pinoLogger.error(args, msg),
};Runtime Compatibility
The SDK works in the following runtimes:
- Node.js 18+
- Vercel
- Cloudflare Workers
- Deno v1.25+
- Bun 1.0+
- React Native
Customizing Fetch Client
The SDK provides a way for you to customize the underlying HTTP client / Fetch function. If you're running in an unsupported environment, this provides a way for you to break glass and ensure the SDK works.
import { TrueFoundryClient } from "truefoundry-sdk";
const client = new TrueFoundryClient({
...
fetcher: // provide your implementation here
});Contributing
While we value open-source contributions to this SDK, this library is generated programmatically. Additions made directly to this library would have to be moved over to our generation code, otherwise they would be overwritten upon the next generated release. Feel free to open a PR as a proof of concept, but know that we will not be able to merge it as-is. We suggest opening an issue first to discuss with us!
On the other hand, contributions to the README are always very welcome!
