Setup Dagger #
Install and verify Dagger, select its version, and publish PATH for CI/CD tasks. Requires FluentCI v0.17.2+; implemented as a typed PureScript Wasm component.
fluentci run setup-dagger setup --version 0.21.11
fluentci run setup-dagger setup --help
Official Dagger archives for Linux/macOS on x86_64 and aarch64.
The default is latest; exact versions may include v. Archive installations
use $HOME/.local/share/fluentci/dagger/VERSION or an absolute --install-dir.
Existing installations are verified before reuse. Downloads verify SHA-256 when
provided by the GitHub release API.
Version mismatches and unavailable release assets fail the operation.
This installs the Dagger CLI. Pipeline execution requires a reachable Dagger engine and its supported container runtime; installing the CLI does not provision or start an engine.
Returns tool, version, bin-dir, and environment. Environment changes apply
to the host session; separate processes must propagate the returned environment.
See COMPONENT.md for every named argument and return type.
Upstream releases · MIT 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-dagger --path /path/to/fluentci-modules/setup/dagger
For a published module, use fluentci add @fluentci.io/setup-dagger@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 dagger 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.SetupDagger as SetupDagger
run :: Effect String
run =
Flow.pipeline "setup-dagger-setup"
# Flow.workdir "."
# SetupDagger.setup (SetupDagger.setupArgs)
# Flow.map (\result -> result.version)
# Flow.run
Gleam #
import fluentci/flow
import fluentci_modules/setup_dagger
pub fn run() -> String {
flow.pipeline("setup-dagger-setup")
|> flow.workdir(".")
|> setup_dagger.setup(setup_dagger.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.SetupDagger
defplugin run do
Flow.pipeline("setup-dagger-setup")
|> Flow.workdir(".")
|> SetupDagger.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-dagger :as setup_dagger]))
(defn run []
(-> (flow/pipeline "setup-dagger-setup")
(flow/workdir ".")
(setup_dagger/setup {})
flow/run!))
ReScript #
let run = (): string =>
Flow.pipeline("setup-dagger-setup")
->Flow.workdir(".")
->FluentciModulesSetupDagger.setup(FluentciModulesSetupDagger.setupArgs)
->Flow.map(result => result.version)
->Flow.run
Python #
from fluentci.flow import pipeline
from fluentci_modules import setup_dagger
def run() -> str:
return (
pipeline("setup-dagger-setup")
.workdir(".")
.pipe(setup_dagger.setup, {})
.map(lambda result: result.version)
.run()
)
TypeScript #
import * as flow from "./fluentci_modules/flow";
import * as setup_dagger from "./fluentci_modules/setup-dagger/index";
export function run(): string {
return flow.pipeline("setup-dagger-setup")
.workdir(".")
.pipe(setup_dagger.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 dagger, select its version, and publish its environment for subsequent tasks. |