@rainbow-o23/n2 v1.0.45

o23/n2

In simple terms, o23/n2 is a tool that publishes a given pipeline as a web application using NestJS. In this module, we handle the following tasks:

• Registering all pipelines and exposing the specified ones as REST APIs,
• Redirecting logs to standard web log output,
• Providing standard error handling, where all errors will be caught and processed uniformly,
• Providing a health check API and a version API,
• Providing a standard pipeline invocation API. Please note that this API is fully compatible with all data processing pipelines but not with file processing pipelines.

Request

Support request parsing as following:

• API path,
• Method,
• Request headers,
• Path parameters,
• Query string parameters,
• Files,
• Json body.

The thing to note is that when multiple types of request data are enabled, o23/n2 will degrade and merge them into a single JSON object, and each part has its own naming conventions as follows:

• Request headers: headers, or given names,
• Path parameters: pathParams, or given names,
• Query string parameters: queryParams, or given names,
• Files: file for single file, files for multiple files, or given names,
• Json body: body.

Response

Support response outputs as following:

• Response headers,
• File download,
• Json body.

APIs

Health Check

- URL: /
- Method: Get
- Response: { up: true, message: 'Hello there, I am OK now.' }

App Version

- URL: /version
- Method: Get
- Response: { version: 'UNDOCUMENTED', builtAt: 'UNDOCUMENTED' }

Pipeline Trigger

- URL: /pipeline
- Method: Post
- Request: { code: 'string'; payload: 'any' }
- Response: 'any'

The specific data format for the request payload and response depends on the pipeline that needs to be executed.

Referring to the example in o23/scaffold on how to build an application based on o23/n2, won't go into detail here.

Environment Parameters