A collection of +180 reusable WebAssembly modules for building composable CI/CD pipelines with FluentCI fluentci.io/modules
modules setup xata README.md
6.3 kB · 191 lines
Markdown
at main

Setup Xata #

Install and verify the Xata CLI and publish PATH for CI/CD pipelines. Implemented in PureScript as a typed Wasm component for FluentCI v0.17.2+.

fluentci run setup-xata setup --version 1.18.2
fluentci run setup-xata setup --help

Official standalone binaries for Linux with glibc and macOS, on x86_64 or aarch64.

Uses the official Xata version manifest and requires its SHA-256 checksum. The selected binary is verified with xata --version. Alpine/musl binaries are unavailable; Alpine is rejected before download. This installs the current Postgres platform CLI, rather than the older npm CLI.

The default is latest; exact releases may include v. Per-user installations use $HOME/.local/share/fluentci/xata/VERSION or an absolute --install-dir. Existing installations are verified before reuse. Version mismatches, checksum failures, and missing platform assets fail setup. No authentication, database creation, or database server installation occurs during setup.

FreeBSD, NetBSD, and OpenBSD attempt the native xata package when available; upstream provides no BSD binary. Repository availability determines whether this works. Native packages use their system prefix; omit --install-dir, optionally select an available package using --package-name, and use --sudo for noninteractive elevation when needed. Unavailable packages fail clearly.

Returns tool, version, bin-dir, and environment. Environment changes apply to subsequent host tasks; separate processes must propagate the returned variables. See COMPONENT.md for all typed arguments and returns.

Use the database module for pipeline operations. SQL clients required by native shell/connect commands remain runner prerequisites.

Upstream CLI · MIT wrapper license.

Compose this module from code #

Requires FluentCI 0.17.6 or newer for generated pipeline bindings. From your caller module's directory, add the dependency:

fluentci add setup-xata --path /path/to/fluentci-modules/setup/xata

For a published module, use fluentci add @fluentci.io/setup-xata@VERSION with an available version. Commit the caller's manifest and lockfile. FluentCI generates named bindings from the installed component's WIT; no handwritten FFI or CLI subprocess is needed. Include generated source directories in the caller's SDK project. The callee can use a different SDK from the caller.

Provision xata before the build steps that require it. The setup result reports the installed version and executable directory.

Replace the sample organization, paths and identifiers with your own. Configure credentials through your CI secret provider before running authenticated operations. Optional arguments use the callee's defaults, and public list fields use comma-separated strings. See COMPONENT.md for argument descriptions and return types.

These examples use the generated composition API and builder chaining in FluentCI 0.17.6; full cross-SDK compilation and execution coverage is still pending. See composition support and limitations.

PureScript #

module Main where

import Prelude
import Effect (Effect)
import FluentCI.Flow as Flow
import FluentCI.Modules.SetupXata as SetupXata

run :: Effect String
run =
  Flow.pipeline "setup-xata-setup"
    # Flow.workdir "."
    # SetupXata.setup (SetupXata.setupArgs)
    # Flow.map (\result -> result.version)
    # Flow.run

Gleam #

import fluentci/flow
import fluentci_modules/setup_xata

pub fn run() -> String {
  flow.pipeline("setup-xata-setup")
  |> flow.workdir(".")
  |> setup_xata.setup(setup_xata.setup_args())
  |> flow.map(fn(result) { result.version })
  |> flow.run
}

Use Gleam's JavaScript target for the Wasm guest. BEAM escripts used for repository automation are separate from component guests.

Elixir #

defmodule Main do
  use FluentCI.Plugin
  alias FluentCI.Flow
  alias FluentCI.Modules.SetupXata

  defplugin run do
    Flow.pipeline("setup-xata-setup")
    |> Flow.workdir(".")
    |> SetupXata.setup(%{})
    |> Flow.stdout()
  end
end

Elixir compiles this sequence to Rust/Wasm. Its initial Flow API does not yet provide the typed result callbacks or cleanup combinators of the other examples.

ClojureScript #

(ns main.plugin
  (:require [fluentci.flow :as flow]
            [fluentci-modules.setup-xata :as setup_xata]))

(defn run []
  (-> (flow/pipeline "setup-xata-setup")
      (flow/workdir ".")
      (setup_xata/setup {})
      flow/run!))

ReScript #

let run = (): string =>
  Flow.pipeline("setup-xata-setup")
  ->Flow.workdir(".")
  ->FluentciModulesSetupXata.setup(FluentciModulesSetupXata.setupArgs)
  ->Flow.map(result => result.version)
  ->Flow.run

Python #

from fluentci.flow import pipeline
from fluentci_modules import setup_xata


def run() -> str:
    return (
        pipeline("setup-xata-setup")
        .workdir(".")
        .pipe(setup_xata.setup, {})
        .map(lambda result: result.version)
        .run()
    )

TypeScript #

import * as flow from "./fluentci_modules/flow";
import * as setup_xata from "./fluentci_modules/setup-xata/index";

export function run(): string {
  return flow.pipeline("setup-xata-setup")
    .workdir(".")
    .pipe(setup_xata.setup, {})
    .map(result => result.version)
    .run();
}

Python and TypeScript use FluentCI builder chains: .pipe(module.function, args) composes generated module functions with .workdir, .env, and .exec. Functions return a pipeline carrying their typed result. Use a generated result callback (With/_with, or a callback argument in TypeScript/Python) when a later module needs a preceding result; use Flow's map operation to select a result field. Execution begins at run (or the Elixir plugin terminal), in declared order.

Exported functions #

Function Purpose
setup Install and verify xata, select its version, and publish its environment for subsequent tasks.