orion-server 1.4.0

Turn business logic into live REST/Kafka services. Declare workflows as JSON and Orion runs them, with rate limiting, circuit breakers, versioning, and observability built in
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

//! `GET /api/v1/admin/functions` — the catalogue of every function a workflow
//! may name, with the input schema of each one that declares one. Powers
//! tooling (CLI, IDEs, docs) that needs to know what exists and what it
//! accepts.
//!
//! It used to serve the schema registry directly, which listed only the
//! functions Orion input-validates — 18 of the 27 valid names, omitting `map`,
//! `filter`, `parse_json` and the rest (#288). Those are the most-used ones, so
//! a completion source built on this offered the connector functions and none
//! of the ones people type. Engine built-ins now appear with `source: "engine"`
//! and no `input_fields`.

use axum::Json;
use serde_json::Value;

use crate::errors::OrionError;
use crate::server::routes::openapi::{DataEnvelope, FunctionSchemaItem};
use crate::server::routes::response_helpers::data_response;

#[utoipa::path(
    get,
    path = "/api/v1/admin/functions",
    tag = "Functions",
    responses(
        (status = 200, description = "Registered workflow function schemas", body = DataEnvelope<Vec<FunctionSchemaItem>>)
    )
)]
#[tracing::instrument]
pub(crate) async fn list_functions() -> Result<Json<Value>, OrionError> {
    Ok(data_response(crate::engine::functions::schema::catalogue()))
}