Skip to content

Catalog WorkflowTemplates

Every WorkflowTemplate in the Dagweave catalog. Search by name or filter by category. Each is an Argo Workflows WorkflowTemplate, and you set its parameters on the step that uses it.

Six are free. The rest need Production or Business. WorkflowTemplate catalog and marketplace names the six and explains how catalog steps work, including why they have no ports.

74 templates

  • Download and unpack a datasetv1.0.0AI

    Download a dataset archive from a URL and unpack it (.tar.gz, .tgz, .tar or .zip) into a destination directory, with an optional bearer token read from a Kubernetes Secret. Unlike download-file, this item also extracts the archive so a downstream step sees the unpacked dataset tree.

    dataset-download
    Changelog
    • v1.0.02026-07-17Initial release.
  • Embed text (OpenAI-compatible)v1.0.2AI

    Get an embedding vector for a piece of text from an OpenAI-compatible embeddings endpoint and echo the raw JSON response. Provider-neutral: configure the base URL and model to target OpenAI or any OpenAI-compatible gateway. The API key is read from a Kubernetes Secret.

    embed-text
    Changelog
    • v1.0.22026-09-12Move to badouralix/curl-jq:ubuntu. The Alpine build this pinned carries two jq advisories on the path this item takes, and its publisher has not rebuilt it since 1 July. The ubuntu tag has neither, and fixable CRITICAL/HIGH drops from 4 to 2. It is Ubuntu 24.04 rather than Alpine, so sh is dash rather than busybox ash, curl goes back from 8.21.0 to 8.5.0 and jq from 1.8.1 to 1.7.1. Still runs as root.
    • v1.0.12026-08-02Swap the abandoned dwdraju/alpine-curl-jq, last built 2025-02-21, for badouralix/curl-jq, which is still being rebuilt. Fixable CRITICAL/HIGH drops from 19 to 1. Same Alpine base, same root user, same /bin/sh default command; curl goes 8.12.1 to 8.21.0 and jq 1.7.1 to 1.8.1.
    • v1.0.02026-07-17Initial release.
  • HuggingFace Inference APIv1.0.3AI

    Run inference on a HuggingFace-hosted model via the HuggingFace Inference API, posting an input text and echoing the raw JSON response. The access token is read from a Kubernetes Secret.

    huggingface-inference
    Changelog
    • v1.0.32026-09-12Move to badouralix/curl-jq:ubuntu. The Alpine build this pinned carries two jq advisories on the path this item takes, and its publisher has not rebuilt it since 1 July. The ubuntu tag has neither, and fixable CRITICAL/HIGH drops from 4 to 2. It is Ubuntu 24.04 rather than Alpine, so sh is dash rather than busybox ash, curl goes back from 8.21.0 to 8.5.0 and jq from 1.8.1 to 1.7.1. Still runs as root.
    • v1.0.22026-08-02Swap the abandoned dwdraju/alpine-curl-jq, last built 2025-02-21, for badouralix/curl-jq, which is still being rebuilt. Fixable CRITICAL/HIGH drops from 19 to 1. Same Alpine base, same root user, same /bin/sh default command; curl goes 8.12.1 to 8.21.0 and jq 1.7.1 to 1.8.1.
    • v1.0.12026-07-17Fix inference endpoint: the legacy api-inference.huggingface.co host was retired (no longer resolves). Point at the current router.huggingface.co/hf-inference/models/<model> endpoint.
    • v1.0.02026-07-17Initial release.
  • Prompt an LLM (OpenAI-compatible)v1.0.2AI

    Send a prompt to an OpenAI-compatible chat completions endpoint and echo the raw JSON response. Provider-neutral: configure the base URL and model to target OpenAI, Azure OpenAI, or any OpenAI-compatible gateway (vLLM, LiteLLM, OpenRouter, ...). The API key is read from a Kubernetes Secret.

    llm-prompt
    Changelog
    • v1.0.22026-09-12Move to badouralix/curl-jq:ubuntu. The Alpine build this pinned carries two jq advisories on the path this item takes, and its publisher has not rebuilt it since 1 July. The ubuntu tag has neither, and fixable CRITICAL/HIGH drops from 4 to 2. It is Ubuntu 24.04 rather than Alpine, so sh is dash rather than busybox ash, curl goes back from 8.21.0 to 8.5.0 and jq from 1.8.1 to 1.7.1. Still runs as root.
    • v1.0.12026-08-02Swap the abandoned dwdraju/alpine-curl-jq, last built 2025-02-21, for badouralix/curl-jq, which is still being rebuilt. Fixable CRITICAL/HIGH drops from 19 to 1. Same Alpine base, same root user, same /bin/sh default command; curl goes 8.12.1 to 8.21.0 and jq 1.7.1 to 1.8.1.
    • v1.0.02026-07-17Initial release.
  • Upsert a vector to a vector DBv1.0.2AI

    Upsert a single vector (with an id and JSON metadata payload) into a vector database via its REST API. Targets the Qdrant points-upsert API (PUT /collections/<collection>/points, `api-key` header); the request body is assembled with jq. The API key is read from a Kubernetes Secret.

    vector-upsert
    Changelog
    • v1.0.22026-09-12Move to badouralix/curl-jq:ubuntu. The Alpine build this pinned carries two jq advisories on the path this item takes, and its publisher has not rebuilt it since 1 July. The ubuntu tag has neither, and fixable CRITICAL/HIGH drops from 4 to 2. It is Ubuntu 24.04 rather than Alpine, so sh is dash rather than busybox ash, curl goes back from 8.21.0 to 8.5.0 and jq from 1.8.1 to 1.7.1. Still runs as root.
    • v1.0.12026-08-02Swap the abandoned dwdraju/alpine-curl-jq, last built 2025-02-21, for badouralix/curl-jq, which is still being rebuilt. Fixable CRITICAL/HIGH drops from 19 to 1. Same Alpine base, same root user, same /bin/sh default command; curl goes 8.12.1 to 8.21.0 and jq 1.7.1 to 1.8.1.
    • v1.0.02026-07-17Initial release.
  • Conditional (when) gatev1.0.0Approval

    Echoes a value only when a condition input is truthy, and is skipped otherwise.

    conditional-when
    Changelog
    • v1.0.02026-07-16Initial release.
  • Request approval in Slackv1.0.1Approval

    Post an approval-request message to a Slack channel, then pause the workflow at an Argo suspend node until a human resumes it.

    slack-approval
    Changelog
    • v1.0.12026-08-02Move curlimages/curl from 8.11.1 to 8.21.0. Fixable CRITICAL/HIGH drops from 26 to 1.
    • v1.0.02026-07-16Initial release.
  • Wait for a fixed durationv1.0.0Approval

    Pause the workflow at an Argo suspend node for a fixed duration, then resume automatically.

    timed-wait
    Changelog
    • v1.0.02026-07-16Initial release.
  • Wait for an external HTTP callbackv1.0.0Approval

    Pause the workflow at an Argo suspend node until an external system resumes it over the Argo Server resume API.

    http-callback-gate
    Changelog
    • v1.0.02026-07-16Initial release.
  • Wait for manual approvalv1.0.0Approval

    Pause the workflow at an Argo suspend node until a human approves it (via the Argo UI, `argo resume`, or the resume API).

    manual-approval
    Changelog
    • v1.0.02026-07-16Initial release.
  • Build and push a container imagev2.0.0CI/CD

    Build a container image from a Dockerfile with BuildKit and push it to a registry, using a Docker config.json read from a Kubernetes Secret.

    docker-build-push
    Changelog
    • v2.0.02026-08-06Replace Kaniko with rootless BuildKit. Google archived kaniko, so its 112 fixable CRITICAL/HIGH (5 CRITICAL) could never come down; BuildKit v0.32.2 measures 64, none CRITICAL, and ships often enough for that to move. Breaking on three counts, hence the major. A context is now a directory or a git/HTTP URL, so kaniko's s3://, gs:// and dir:// contexts are gone and its git:// prefix now means the git wire protocol rather than "clone over HTTPS"; a git subdirectory rides in the URL fragment as `#ref:subdir` where kaniko took a separate --context-sub-path. The container needs Unconfined seccomp and AppArmor to unshare a user namespace, which kaniko did not, so it will not admit into a namespace enforcing PodSecurity `restricted`. New `push` parameter, default "true", standing in for kaniko's --no-push.
    • v1.0.12026-08-02Move kaniko from v1.23.2 to v1.24.0, the newest release. Fixable CRITICAL/HIGH only drops from 116 to 112: kaniko has shipped nothing since May 2025, so clearing the rest needs a different build tool rather than another bump.
    • v1.0.02026-07-17Initial release.
  • Bump a semantic versionv1.0.0CI/CD

    Compute the next semantic version from a base version and a bump type (major/minor/patch), exposing the result as an Argo output parameter for downstream steps.

    semver-bump
    Changelog
    • v1.0.02026-07-17Initial release.
  • Lint a Dockerfilev1.0.0CI/CD

    Check a Dockerfile against Hadolint's rules for common mistakes and bad practice, and fail the step at the severity you choose.

    hadolint-lint
    Changelog
    • v1.0.02026-10-18Initial release.
  • Publish a build artifactv1.0.1CI/CD

    Upload a build artifact to an artifact registry with an HTTP PUT via curl, using credentials read from a Kubernetes Secret.

    publish-artifact
    Changelog
    • v1.0.12026-08-02Move curlimages/curl from 8.11.1 to 8.21.0. Fixable CRITICAL/HIGH drops from 26 to 1.
    • v1.0.02026-07-17Initial release.
  • Run a Node.js scriptv1.0.0CI/CD

    Run a Node.js script you paste in, in a working directory of your choice, after installing any npm packages you list.

    node-script
    Changelog
    • v1.0.02026-10-18Initial release.
  • Run a Python scriptv1.0.0CI/CD

    Run a Python script you paste in, in a working directory of your choice, after installing any pip packages you list.

    python-script
    Changelog
    • v1.0.02026-10-18Initial release.
  • Run a test commandv1.0.2CI/CD

    Run a test command in a working directory on a generic Node 24 image. Swap the image for a different toolchain.

    run-shell-tests
    Changelog
    • v1.0.22026-09-12Repin node:24-alpine to the digest the tag now points at. The old pin had fallen behind its tag, which the CVE gate reads as an OS record whose reason is spent. The new bytes carry the same openssl advisory and the same four npm advisories as the old ones, so a test command sees the same Node 24.
    • v1.0.12026-08-02Move node from 20-alpine to 24-alpine. Fixable CRITICAL/HIGH drops from 18 to 5. This crosses majors: Node 20 left maintenance and no 20.x rebuild carries the fixes, so a test command that relies on Node 20 behaviour needs rechecking.
    • v1.0.02026-07-17Initial release.
  • Scan for vulnerabilities with Trivyv1.0.3CI/CD

    Scan a container image or a filesystem path for known vulnerabilities with Trivy, optionally failing the step on findings.

    trivy-scan
    Changelog
    • v1.0.32026-08-18Move trivy from 0.73.0 to 0.74.0. The image scans clean, so its exception record is deleted rather than rewritten: the go-git and oras-go advisories it was written for are gone, and so are the eight Go 1.26.6 stdlib ones that had landed on 0.73.0 since. Entrypoint, Cmd, User and WorkingDir are identical on both digests. This is a minor rather than a rebuild, so the CLI surface has not been re-run against a container.
    • v1.0.22026-08-11Move trivy from 0.72.0 to 0.73.0. Clears all 9 fixable OS advisories and takes the vendored ones from 6 to 2. The minor changes no CLI surface: image mode, fs mode, --severity and --exit-code all behave identically on both digests, exit code included.
    • v1.0.12026-08-02Move trivy from 0.58.1 to 0.72.0. Fixable CRITICAL/HIGH drops from 91 to 11. Worth doing on its own terms too: the scanner this item sells was fourteen minor releases behind.
    • v1.0.02026-07-17Initial release.
  • Sign a container imagev1.0.0CI/CD

    Sign a container image in its registry with a cosign key pair, so that anyone with the public key can check it came from you. The private key and its password come from a Kubernetes Secret.

    cosign-sign
    Changelog
    • v1.0.02026-10-18Initial release.
  • Verify a container image signaturev1.0.0CI/CD

    Check that a container image carries a valid cosign signature from your public key, and fail the step if it does not. Use it before deploying an image you did not just build.

    cosign-verify
    Changelog
    • v1.0.02026-10-18Initial release.
  • Gzip a filev1.0.0Data

    Compress a local file or artifact with gzip, writing the result to a destination path.

    gzip-compress
    Changelog
    • v1.0.02026-07-16Initial release.
  • Run a SQL query and write results to S3 as CSVv1.1.2Data

    Run a SQL query against a Postgres database and write the result set to Amazon S3 as a CSV object. Connection string and AWS credentials are read from Kubernetes Secrets.

    sql-to-s3
    Changelog
    • v1.1.22026-10-16Repin python on 3.15-slim and move psycopg2-binary 2.9.12 to 2.9.13, the first release with CPython 3.15 wheels. 2.9.12 had none, so pip fell back to building it from source and failed for want of pg_config.
    • v1.1.12026-08-18Repin python:3.13-slim on the current digest, in ./Dockerfile as well as here. Same tag, CPython 3.13.14 to 3.13.15, and Entrypoint, Cmd, User and WorkingDir are identical on both. The repin clears nothing: util-linux CVE-2026-53615 is on the new bytes too. What it buys is a record that holds, because an OS baseline covers a pin only while that pin is its tag's head, and this one had fallen behind. pip also moves 26.1.2 to 26.2.1, which ships an SBOM of its vendored tree, so trivy now reports the msgpack and setuptools the old pin already vendored without declaring; both are recorded in hack/image-cve-exceptions.txt. This is the one item that runs pip, and it runs it with --no-cache-dir, which is the cache msgpack serialises. psycopg2-binary 2.9.12 and boto3 1.43.68 both resolve to wheels on this interpreter, so no sdist build runs either.
    • v1.1.02026-08-12Cut ahead of the first image push: build-item-images reads the tag it pushes out of this file, so the version has to move before the dispatch or the first tag names the release that installs psycopg2-binary and boto3 from PyPI on every run. The template still does that install. It moves onto the image, and this entry gets the digest, once the package exists and is public.
    • v1.0.12026-08-11Pin psycopg2-binary to 2.9.12 and boto3 to 1.43.68 in the run-time install. They floated, so the digest froze the image and not the code that ran in it.
    • v1.0.02026-07-16Initial release.
  • Run data-quality assertions on a datasetv1.0.1Data

    Run basic data-quality assertions on a CSV dataset, per-column null fraction and minimum row count, and fail the step when a rule is violated.

    data-quality-check
    Changelog
    • v1.0.12026-08-18Repin python:3.13-slim on the current digest. Same tag, CPython 3.13.14 to 3.13.15, and Entrypoint, Cmd, User and WorkingDir are identical on both. The repin clears nothing: util-linux CVE-2026-53615 is on the new bytes too. What it buys is a record that holds, because an OS baseline covers a pin only while that pin is its tag's head, and this one had fallen behind. pip also moves 26.1.2 to 26.2.1, which ships an SBOM of its vendored tree, so trivy now reports the msgpack and setuptools the old pin already vendored without declaring; both are recorded in hack/image-cve-exceptions.txt. This item runs python -c over the stdlib and never invokes pip.
    • v1.0.02026-07-16Initial release.
  • Transform JSON with a jq filterv1.0.0Data

    Transform a JSON document by applying a jq program, printing the result to stdout.

    json-transform
    Changelog
    • v1.0.02026-07-16Initial release.
  • Validate a CSV's headers and row countv1.0.1Data

    Validate that a CSV document has a header row containing a required set of columns and at least a minimum number of data rows; fails the step otherwise.

    csv-validate
    Changelog
    • v1.0.12026-08-18Repin python:3.13-slim on the current digest. Same tag, CPython 3.13.14 to 3.13.15, and Entrypoint, Cmd, User and WorkingDir are identical on both. The repin clears nothing: util-linux CVE-2026-53615 is on the new bytes too. What it buys is a record that holds, because an OS baseline covers a pin only while that pin is its tag's head, and this one had fallen behind. pip also moves 26.1.2 to 26.2.1, which ships an SBOM of its vendored tree, so trivy now reports the msgpack and setuptools the old pin already vendored without declaring; both are recorded in hack/image-cve-exceptions.txt. This item runs python -c over the stdlib and never invokes pip.
    • v1.0.02026-07-16Initial release.
  • Back up PostgreSQL to S3v1.0.0Databases

    Dump a PostgreSQL database with pg_dump and upload the dump file to an S3 bucket. Restore it with pg_restore.

    pg-dump-to-s3
    Changelog
    • v1.0.02026-10-18Initial release.
  • Run a BigQuery queryv1.0.4Databases

    Run a Standard SQL query against BigQuery with the bq CLI, using a GCP service-account key read from a Kubernetes Secret.

    bigquery-query
    Changelog
    • v1.0.42026-08-20Repin google/cloud-sdk:slim onto 581.0.0-slim, the digest :slim now heads at. gcloud goes 580.0.0 to 581.0.0 on the same Dockerfile: Entrypoint, Cmd, User and WorkingDir match across both digests and the only layers that differ are the ones carrying the version argument. The four util-linux advisories the old pin went red on, CVE-2026-53612 through CVE-2026-53615, are gone with Debian's 2.41.5-0+deb13u1, so the OS baseline record is deleted rather than rewritten. The eleven vendored advisories are the same eleven on both digests and keep their record.
    • v1.0.32026-08-11Repin google/cloud-sdk:slim on the current digest, which is also the newest 580.0.0-slim. gcloud goes 579.0.0 to 580.0.0 and bq stays at 2.1.36. The last fixable OS-package HIGH, linux-libc-dev CVE-2026-64561, is gone with the newer Debian trixie base, so the OS baseline record is deleted rather than rewritten. The three cryptography advisories in the bundled Python are unmoved and keep their record.
    • v1.0.22026-08-11Repin google/cloud-sdk:slim on the current digest. Same tag, newer build. Fixable OS-package HIGH drops from 21 to 1: the libexpat1 and linux-libc-dev updates have landed, one newer linux-libc-dev has not. gcloud goes 578.0.0 to 579.0.0 and bq stays at 2.1.36.
    • v1.0.12026-08-02Repin google/cloud-sdk:slim on the current digest. Same tag, newer build. Fixable CRITICAL/HIGH drops from 37 to 18.
    • v1.0.02026-07-17Initial release.
  • Run a MongoDB findv1.0.2Databases

    Run a find() query against a MongoDB collection with mongosh, using a connection URI (with credentials) read from a Kubernetes Secret.

    mongodb-query
    Changelog
    • v1.0.22026-10-19Repin mongo:7 on the tag's current digest. What is still open against it is recorded in hack/image-cve-exceptions.txt. Same tool, same arguments; nothing about what the step runs changes.
    • v1.0.12026-08-02Repin mongo:7 on the current digest. Same tag, newer build, and the fixable CVE count does not move: still 192, because upstream has not shipped the fixes. Worth doing anyway so the pin is not a year behind the tag.
    • v1.0.02026-07-17Initial release.
  • Run a MySQL queryv1.0.1Databases

    Run a SQL query against a MySQL database with the mysql client, using a password read from a Kubernetes Secret.

    mysql-query
    Changelog
    • v1.0.12026-08-02Repin mysql:8 on the current digest. Same tag, newer build. Fixable CRITICAL/HIGH drops from 22 to 19.
    • v1.0.02026-07-17Initial release.
  • Run a PostgreSQL queryv1.0.0Databases

    Run a SQL query against a PostgreSQL database with psql, using a password read from a Kubernetes Secret.

    postgres-query
    Changelog
    • v1.0.02026-07-17Initial release.
  • Run a Redis commandv1.0.0Databases

    Run a command against a Redis server with redis-cli, using an AUTH password read from a Kubernetes Secret.

    redis-command
    Changelog
    • v1.0.02026-07-17Initial release.
  • Vacuum and analyze PostgreSQLv1.0.0Databases

    Reclaim dead space and refresh the planner's statistics on a PostgreSQL database, or on the tables you list.

    pg-vacuum-analyze
    Changelog
    • v1.0.02026-10-18Initial release.
  • Check out a git repositoryv1.0.2Git

    Clone a git repository and check out a branch, tag, or commit into a path. Credentials (username/password, e.g. a personal access token) are read from a Kubernetes Secret; leave them blank for a public repo. Converted from the built-in dagweave "Check out a git repository" blueprint.

    git-checkout
    Changelog
    • v1.0.22026-10-19Repin alpine/git:2.54.0 on the tag's current digest. What is still open against it is recorded in hack/image-cve-exceptions.txt. Same tool, same arguments; nothing about what the step runs changes.
    • v1.0.12026-08-02Move alpine/git from 2.45.2 to 2.54.0. Clears all 55 fixable CRITICAL/HIGH; the image now scans clean.
    • v1.0.02026-07-17Initial release. Converted from the built-in git-checkout blueprint.
  • Commit and push a working directoryv1.0.2Git

    Commit the changes in a checked-out working directory and push HEAD to a branch on its remote. Author identity and target branch are configurable; credentials come from a Kubernetes Secret. Converted from the built-in dagweave "Commit and push a working directory" blueprint.

    git-commit-push
    Changelog
    • v1.0.22026-10-19Repin alpine/git:2.54.0 on the tag's current digest. What is still open against it is recorded in hack/image-cve-exceptions.txt. Same tool, same arguments; nothing about what the step runs changes.
    • v1.0.12026-08-02Move alpine/git from 2.45.2 to 2.54.0. Clears all 55 fixable CRITICAL/HIGH; the image now scans clean.
    • v1.0.02026-07-17Initial release. Converted from the built-in git-commit-push blueprint.
  • Open a GitHub pull requestv1.0.1Git

    Open a pull request on GitHub via the REST API (POST /repos/{owner}/{repo}/pulls), using a token read from a Kubernetes Secret. Inputs are the repo, head and base branches, and the PR title/body.

    open-github-pr
    Changelog
    • v1.0.12026-08-02Move curlimages/curl from 8.11.1 to 8.21.0. Fixable CRITICAL/HIGH drops from 26 to 1.
    • v1.0.02026-07-17Initial release.
  • Shallow-clone a git repositoryv1.0.2Git

    Shallow-clone a single branch or tag of a git repository to a configurable depth and destination path. Credentials are read from a Kubernetes Secret; leave them blank for a public repo.

    git-clone
    Changelog
    • v1.0.22026-10-19Repin alpine/git:2.54.0 on the tag's current digest. What is still open against it is recorded in hack/image-cve-exceptions.txt. Same tool, same arguments; nothing about what the step runs changes.
    • v1.0.12026-08-02Move alpine/git from 2.45.2 to 2.54.0. Clears all 55 fixable CRITICAL/HIGH; the image now scans clean.
    • v1.0.02026-07-17Initial release.
  • Tag a ref and push the tagv1.0.2Git

    Create an annotated git tag at a ref and push it to the remote. Clones the repository, tags it, and pushes the tag using credentials from a Kubernetes Secret.

    git-tag
    Changelog
    • v1.0.22026-10-19Repin alpine/git:2.54.0 on the tag's current digest. What is still open against it is recorded in hack/image-cve-exceptions.txt. Same tool, same arguments; nothing about what the step runs changes.
    • v1.0.12026-08-02Move alpine/git from 2.45.2 to 2.54.0. Clears all 55 fixable CRITICAL/HIGH; the image now scans clean.
    • v1.0.02026-07-17Initial release.
  • Check a TLS certificate's expiryv1.0.0HTTP

    Connect to a host over TLS and fail the step if its certificate expires within the number of days you set. Passes the days left to later steps.

    tls-cert-expiry-check
    Changelog
    • v1.0.02026-10-18Initial release.
  • Download a filev1.0.1HTTP

    Download a file from a URL to a filesystem path (following redirects), with an optional bearer token read from a Kubernetes Secret.

    download-file
    Changelog
    • v1.0.12026-08-02Move curlimages/curl from 8.11.1 to 8.21.0. Fixable CRITICAL/HIGH drops from 26 to 1.
    • v1.0.02026-07-17Initial release.
  • HTTP request (curl)v1.0.1HTTP

    Make a generic HTTP request (any method) to a URL with an optional body, configurable Content-Type, and an optional bearer token read from a Kubernetes Secret.

    http-request-curl
    Changelog
    • v1.0.12026-08-02Move curlimages/curl from 8.11.1 to 8.21.0. Fixable CRITICAL/HIGH drops from 26 to 1.
    • v1.0.02026-07-17Initial release.
  • POST JSON to a webhookv1.0.1HTTP

    POST a JSON payload to an arbitrary webhook URL, with an optional Authorization header read from a Kubernetes Secret.

    webhook-post
    Changelog
    • v1.0.12026-08-02Move curlimages/curl from 8.11.1 to 8.21.0. Fixable CRITICAL/HIGH drops from 26 to 1.
    • v1.0.02026-07-17Initial release.
  • Poll a URL until a condition holdsv1.0.2HTTP

    Repeatedly GET a URL and evaluate a jq boolean filter over the JSON response, succeeding when the condition becomes truthy or failing after a maximum number of attempts. Useful for waiting on an async job or a resource to reach a desired state.

    rest-poll-until
    Changelog
    • v1.0.22026-09-12Move to badouralix/curl-jq:ubuntu. The Alpine build this pinned carries two jq advisories on the path this item takes, and its publisher has not rebuilt it since 1 July. The ubuntu tag has neither, and fixable CRITICAL/HIGH drops from 4 to 2. It is Ubuntu 24.04 rather than Alpine, so sh is dash rather than busybox ash, curl goes back from 8.21.0 to 8.5.0 and jq from 1.8.1 to 1.7.1. A jq-condition that needs something new in jq 1.8 stops working. Still runs as root.
    • v1.0.12026-08-02Swap the abandoned dwdraju/alpine-curl-jq, last built 2025-02-21, for badouralix/curl-jq, which is still being rebuilt. Fixable CRITICAL/HIGH drops from 19 to 1. Same Alpine base, same root user, same /bin/sh default command; curl goes 8.12.1 to 8.21.0 and jq 1.7.1 to 1.8.1.
    • v1.0.02026-07-17Initial release.
  • Run a GraphQL queryv1.0.2HTTP

    POST a GraphQL query (or mutation) with JSON variables to a GraphQL endpoint, authenticated with a bearer token read from a Kubernetes Secret. The request body is assembled with jq so quotes and newlines in the query are escaped safely.

    graphql-query
    Changelog
    • v1.0.22026-09-12Move to badouralix/curl-jq:ubuntu. The Alpine build this pinned carries two jq advisories on the path this item takes, and its publisher has not rebuilt it since 1 July. The ubuntu tag has neither, and fixable CRITICAL/HIGH drops from 4 to 2. It is Ubuntu 24.04 rather than Alpine, so sh is dash rather than busybox ash, curl goes back from 8.21.0 to 8.5.0 and jq from 1.8.1 to 1.7.1. Still runs as root.
    • v1.0.12026-08-02Swap the abandoned dwdraju/alpine-curl-jq, last built 2025-02-21, for badouralix/curl-jq, which is still being rebuilt. Fixable CRITICAL/HIGH drops from 19 to 1. Same Alpine base, same root user, same /bin/sh default command; curl goes 8.12.1 to 8.21.0 and jq 1.7.1 to 1.8.1.
    • v1.0.02026-07-17Initial release.
  • Back up a cluster with Velerov1.0.0Kubernetes

    Ask Velero to back up some or all namespaces, wait for the backup to finish, and fail the step unless it completes cleanly. Passes the backup name to later steps.

    velero-backup
    Changelog
    • v1.0.02026-10-18Initial release.
  • Cordon or uncordon a nodev1.0.0Kubernetes

    Stop new pods from landing on a node, or let them land on it again, without touching the pods already there.

    kubectl-cordon-node
    Changelog
    • v1.0.02026-10-18Initial release.
  • Drain a nodev1.0.0Kubernetes

    Mark a node unschedulable and move its pods to other nodes, so the node can be patched, rebooted or removed.

    kubectl-drain-node
    Changelog
    • v1.0.02026-10-18Initial release.
  • Helm upgrade --installv1.0.4Kubernetes

    Install or upgrade a Helm release with `helm upgrade --install`, using the workflow pod's in-cluster serviceAccount. Supports an optional chart repo URL and inline values.yaml.

    helm-upgrade
    Changelog
    • v1.0.42026-10-19Move alpine/helm 3.22.0 to 3.22.1, the current head of that tag. What is still open against it is recorded in hack/image-cve-exceptions.txt. Same tool, same arguments; nothing about what the step runs changes.
    • v1.0.32026-09-10Declare localSupport unsupported with its reason, and write the same pair onto the entrypoint template as dagweave.io/local-support annotations. Dagweave Local's lint rules on the compiled pod spec and so cannot see a command that shells out to helm, which leaves the item to say it itself. Template metadata only; nothing about what this runs on a real cluster changes.
    • v1.0.22026-08-18Move alpine/helm from 3.21.3 to 3.21.4. Clears x/text CVE-2026-56852 and leaves the eight Go 1.26.6 stdlib advisories exactly where they were, because 3.21.4 is a rebuild on the same 1.26.5 toolchain; vendored HIGH goes 10 to 9 and is recorded in hack/image-cve-exceptions.txt. Taken as much for the tag as for the one advisory: the old record claimed 3.21.3 was the newest 3.x and that had stopped being true. Helm 4 is still a major with its own migration.
    • v1.0.12026-08-02Move alpine/helm from 3.16.3 to 3.21.3, the newest 3.x. Fixable CRITICAL/HIGH drops from 76 to 1. Helm 4 exists but is a major with its own migration, so this stays on 3.x.
    • v1.0.02026-07-17Initial release.
  • Read Kubernetes resources as JSONv1.0.0Kubernetes

    Read one resource, or a list of them, from the cluster and pass the JSON to later steps as the json output.

    kubectl-get-json
    Changelog
    • v1.0.02026-10-18Initial release.
  • Render a Kustomize overlayv1.0.0Kubernetes

    Build a Kustomize directory into plain Kubernetes YAML and save it to a file, ready for kubectl-apply or a policy check.

    kustomize-build
    Changelog
    • v1.0.02026-10-18Initial release.
  • Restart a workloadv1.0.0Kubernetes

    Restart a Deployment, StatefulSet or DaemonSet so its pods are replaced one at a time, and optionally wait until the new pods are ready.

    kubectl-rollout-restart
    Changelog
    • v1.0.02026-10-18Initial release.
  • Roll back a workloadv1.0.0Kubernetes

    Roll a Deployment, StatefulSet or DaemonSet back to its previous revision, or to a revision you name, and wait until the old pods are ready again.

    kubectl-rollout-undo
    Changelog
    • v1.0.02026-10-18Initial release.
  • Run a one-off Kubernetes Jobv1.0.0Kubernetes

    Run a command in a container as a Job in the cluster, show its log, and fail the step if the Job fails or does not finish in time. The Job does not retry on its own.

    kubectl-run-job
    Changelog
    • v1.0.02026-10-18Initial release.
  • Scale deploymentv1.0.6Kubernetes

    Scale a Deployment to a target replica count with `kubectl scale`, using the workflow pod's in-cluster serviceAccount.

    scale-deployment
    Changelog
    • v1.0.62026-10-19Repin bitnami/kubectl:latest on the tag's current digest. What is still open against it is recorded in hack/image-cve-exceptions.txt. Same tool, same arguments; nothing about what the step runs changes.
    • v1.0.52026-09-10Declare localSupport unsupported with its reason, and write the same pair onto the entrypoint template as dagweave.io/local-support annotations. Dagweave Local's lint rules on the compiled pod spec and so cannot see a command that shells out to kubectl, which leaves the item to say it itself. Template metadata only; nothing about what this runs on a real cluster changes.
    • v1.0.42026-08-23Repin bitnami/kubectl:latest on the current digest, to clear CVE-2026-14456. That is a HIGH openssl denial of service via unbounded memory, fixed upstream in 3.5.7-5.ph5 and present in openssl and openssl-libs on the old pin. The scheduled CVE scan had been red on it for two fires, 22 and 23 August, and nothing else was failing. Same tag, same kubectl, newer build, and the new digest reports no fixed HIGH or CRITICAL at all so it needs no record in hack/image-cve-exceptions.txt.
    • v1.0.32026-08-18Repin bitnami/kubectl:latest on the current digest. Same tag, same kubectl v1.36.3, newer build. Clears the OS half outright, rpm-libs CVE-2026-44604 on PhotonOS, so this image needs no OS record at all, and takes the eight Go 1.26.6 stdlib advisories with it. Vendored HIGH goes 12 to 6: five x/net and one x/text in the kubectl and yq binaries, recorded in hack/image-cve-exceptions.txt.
    • v1.0.22026-08-11Repin bitnami/kubectl:latest on the current digest. Same tag, same kubectl v1.36.3, newer build. Clears the one fixable OS-package HIGH the old digest carried, libacl CVE-2026-54369. The twelve vendored HIGH in the kubectl and yq binaries are unchanged and recorded in hack/image-cve-exceptions.txt.
    • v1.0.12026-08-02Repin bitnami/kubectl:latest on the current digest. Same tag, newer build. Clears the four CRITICAL CVEs the old digest carried; twelve fixable HIGH are still there.
    • v1.0.02026-07-17Initial release.
  • Sync an Argo CD applicationv1.0.0Kubernetes

    Tell Argo CD to sync an application to its Git source and wait until the sync finishes and the application is healthy. Logs in with an API token from a Kubernetes Secret.

    argocd-sync
    Changelog
    • v1.0.02026-10-18Initial release.
  • Wait for a Kubernetes conditionv1.0.0Kubernetes

    Pause the workflow until a resource reaches a condition such as Ready or Available, and fail the step if the timeout runs out first.

    kubectl-wait-condition
    Changelog
    • v1.0.02026-10-18Initial release.
  • Wait for rolloutv1.0.6Kubernetes

    Block until a Deployment (or StatefulSet/DaemonSet) rollout completes, using `kubectl rollout status` with a timeout and the pod's in-cluster serviceAccount.

    wait-for-rollout
    Changelog
    • v1.0.62026-10-19Repin bitnami/kubectl:latest on the tag's current digest. What is still open against it is recorded in hack/image-cve-exceptions.txt. Same tool, same arguments; nothing about what the step runs changes.
    • v1.0.52026-09-10Declare localSupport unsupported with its reason, and write the same pair onto the entrypoint template as dagweave.io/local-support annotations. Dagweave Local's lint rules on the compiled pod spec and so cannot see a command that shells out to kubectl, which leaves the item to say it itself. Template metadata only; nothing about what this runs on a real cluster changes.
    • v1.0.42026-08-23Repin bitnami/kubectl:latest on the current digest, to clear CVE-2026-14456. That is a HIGH openssl denial of service via unbounded memory, fixed upstream in 3.5.7-5.ph5 and present in openssl and openssl-libs on the old pin. The scheduled CVE scan had been red on it for two fires, 22 and 23 August, and nothing else was failing. Same tag, same kubectl, newer build, and the new digest reports no fixed HIGH or CRITICAL at all so it needs no record in hack/image-cve-exceptions.txt.
    • v1.0.32026-08-18Repin bitnami/kubectl:latest on the current digest. Same tag, same kubectl v1.36.3, newer build. Clears the OS half outright, rpm-libs CVE-2026-44604 on PhotonOS, so this image needs no OS record at all, and takes the eight Go 1.26.6 stdlib advisories with it. Vendored HIGH goes 12 to 6: five x/net and one x/text in the kubectl and yq binaries, recorded in hack/image-cve-exceptions.txt.
    • v1.0.22026-08-11Repin bitnami/kubectl:latest on the current digest. Same tag, same kubectl v1.36.3, newer build. Clears the one fixable OS-package HIGH the old digest carried, libacl CVE-2026-54369. The twelve vendored HIGH in the kubectl and yq binaries are unchanged and recorded in hack/image-cve-exceptions.txt.
    • v1.0.12026-08-02Repin bitnami/kubectl:latest on the current digest. Same tag, newer build. Clears the four CRITICAL CVEs the old digest carried; twelve fixable HIGH are still there.
    • v1.0.02026-07-17Initial release.
  • kubectl applyv1.0.6Kubernetes

    Apply a manifest to the cluster with kubectl, using the workflow pod's in-cluster serviceAccount. Accepts an inline manifest or a path to a manifest file, in a target namespace.

    kubectl-apply
    Changelog
    • v1.0.62026-10-19Repin bitnami/kubectl:latest on the tag's current digest. What is still open against it is recorded in hack/image-cve-exceptions.txt. Same tool, same arguments; nothing about what the step runs changes.
    • v1.0.52026-09-10Declare localSupport unsupported with its reason, and write the same pair onto the entrypoint template as dagweave.io/local-support annotations. Dagweave Local's lint rules on the compiled pod spec and so cannot see a command that shells out to kubectl, which leaves the item to say it itself. Template metadata only; nothing about what this runs on a real cluster changes.
    • v1.0.42026-08-23Repin bitnami/kubectl:latest on the current digest, to clear CVE-2026-14456. That is a HIGH openssl denial of service via unbounded memory, fixed upstream in 3.5.7-5.ph5 and present in openssl and openssl-libs on the old pin. The scheduled CVE scan had been red on it for two fires, 22 and 23 August, and nothing else was failing. Same tag, same kubectl, newer build, and the new digest reports no fixed HIGH or CRITICAL at all so it needs no record in hack/image-cve-exceptions.txt.
    • v1.0.32026-08-18Repin bitnami/kubectl:latest on the current digest. Same tag, same kubectl v1.36.3, newer build. Clears the OS half outright, rpm-libs CVE-2026-44604 on PhotonOS, so this image needs no OS record at all, and takes the eight Go 1.26.6 stdlib advisories with it. Vendored HIGH goes 12 to 6: five x/net and one x/text in the kubectl and yq binaries, recorded in hack/image-cve-exceptions.txt.
    • v1.0.22026-08-11Repin bitnami/kubectl:latest on the current digest. Same tag, same kubectl v1.36.3, newer build. Clears the one fixable OS-package HIGH the old digest carried, libacl CVE-2026-54369. The twelve vendored HIGH in the kubectl and yq binaries are unchanged and recorded in hack/image-cve-exceptions.txt.
    • v1.0.12026-08-02Repin bitnami/kubectl:latest on the current digest. Same tag, newer build. Clears the four CRITICAL CVEs the old digest carried; twelve fixable HIGH are still there.
    • v1.0.02026-07-17Initial release.
  • kubectl deletev1.0.6Kubernetes

    Delete a named Kubernetes resource with kubectl, using the workflow pod's in-cluster serviceAccount. Idempotent via --ignore-not-found.

    kubectl-delete
    Changelog
    • v1.0.62026-10-19Repin bitnami/kubectl:latest on the tag's current digest. What is still open against it is recorded in hack/image-cve-exceptions.txt. Same tool, same arguments; nothing about what the step runs changes.
    • v1.0.52026-09-10Declare localSupport unsupported with its reason, and write the same pair onto the entrypoint template as dagweave.io/local-support annotations. Dagweave Local's lint rules on the compiled pod spec and so cannot see a command that shells out to kubectl, which leaves the item to say it itself. Template metadata only; nothing about what this runs on a real cluster changes.
    • v1.0.42026-08-23Repin bitnami/kubectl:latest on the current digest, to clear CVE-2026-14456. That is a HIGH openssl denial of service via unbounded memory, fixed upstream in 3.5.7-5.ph5 and present in openssl and openssl-libs on the old pin. The scheduled CVE scan had been red on it for two fires, 22 and 23 August, and nothing else was failing. Same tag, same kubectl, newer build, and the new digest reports no fixed HIGH or CRITICAL at all so it needs no record in hack/image-cve-exceptions.txt.
    • v1.0.32026-08-18Repin bitnami/kubectl:latest on the current digest. Same tag, same kubectl v1.36.3, newer build. Clears the OS half outright, rpm-libs CVE-2026-44604 on PhotonOS, so this image needs no OS record at all, and takes the eight Go 1.26.6 stdlib advisories with it. Vendored HIGH goes 12 to 6: five x/net and one x/text in the kubectl and yq binaries, recorded in hack/image-cve-exceptions.txt.
    • v1.0.22026-08-11Repin bitnami/kubectl:latest on the current digest. Same tag, same kubectl v1.36.3, newer build. Clears the one fixable OS-package HIGH the old digest carried, libacl CVE-2026-54369. The twelve vendored HIGH in the kubectl and yq binaries are unchanged and recorded in hack/image-cve-exceptions.txt.
    • v1.0.12026-08-02Repin bitnami/kubectl:latest on the current digest. Same tag, newer build. Clears the four CRITICAL CVEs the old digest carried; twelve fixable HIGH are still there.
    • v1.0.02026-07-17Initial release.
  • Create a Jira issuev1.0.0Notifications

    Open an issue in a Jira Cloud project, for example when a deploy or a test run fails, and pass its key to later steps. Logs in with an email and API token from a Kubernetes Secret.

    jira-create-issue
    Changelog
    • v1.0.02026-10-18Initial release.
  • Post a message to Discordv1.0.1Notifications

    Post a message to a Discord channel via an incoming-webhook URL read from a Kubernetes Secret.

    discord-post
    Changelog
    • v1.0.12026-08-02Move curlimages/curl from 8.11.1 to 8.21.0. Fixable CRITICAL/HIGH drops from 26 to 1.
    • v1.0.02026-07-16Initial release.
  • Post a message to Microsoft Teamsv1.0.0Notifications

    Post a message to a Microsoft Teams channel via an incoming-webhook URL read from a Kubernetes Secret.

    microsoft-teams-post
    Changelog
    • v1.0.02026-07-16Initial release.
  • Post a message to Slackv1.0.1Notifications

    Post a message to a Slack channel via the chat.postMessage Web API, using a bot token read from a Kubernetes Secret.

    slack-post-message
    Changelog
    • v1.0.12026-08-02Move curlimages/curl from 8.11.1 to 8.21.0. Fixable CRITICAL/HIGH drops from 26 to 1.
    • v1.0.02026-07-16Initial release.
  • Publish to an SNS topicv1.0.0Notifications

    Publish a message to an Amazon SNS topic, which fans it out to the topic's subscribers, and pass its message id to later steps.

    sns-publish
    Changelog
    • v1.0.02026-10-18Initial release.
  • Raise an Opsgenie alertv1.0.0Notifications

    Create an alert in Opsgenie so the on-call responder is paged. The API key comes from a Kubernetes Secret.

    opsgenie-alert
    Changelog
    • v1.0.02026-10-18Initial release.
  • Send a Telegram messagev1.0.1Notifications

    Send a message from a Telegram bot to a chat via the Bot API sendMessage method, with the bot token read from a Kubernetes Secret.

    telegram-send
    Changelog
    • v1.0.12026-08-02Move curlimages/curl from 8.11.1 to 8.21.0. Fixable CRITICAL/HIGH drops from 26 to 1.
    • v1.0.02026-07-16Initial release.
  • Send an SQS messagev1.0.0Notifications

    Put a message on an Amazon SQS queue and pass its message id to later steps. Works with standard and FIFO queues.

    sqs-send-message
    Changelog
    • v1.0.02026-10-18Initial release.
  • Send an email via SMTPv1.0.1Notifications

    Send a plain-text email through an authenticated SMTP submission server (STARTTLS), with the password read from a Kubernetes Secret.

    email-send
    Changelog
    • v1.0.12026-08-02Move curlimages/curl from 8.11.1 to 8.21.0. Fixable CRITICAL/HIGH drops from 26 to 1.
    • v1.0.02026-07-16Initial release.
  • Trigger a PagerDuty alertv1.0.0Notifications

    Trigger a PagerDuty incident via the Events API v2, with the integration routing key read from a Kubernetes Secret.

    pagerduty-trigger
    Changelog
    • v1.0.02026-07-16Initial release.
  • Delete S3 objectsv1.0.0Object storage

    Delete one object, or every object under a prefix, from an S3 bucket. Use it to clear old backups or build output.

    s3-delete
    Changelog
    • v1.0.02026-10-18Initial release.
  • Download an object from S3v1.0.2Object storage

    Download an object from an Amazon S3 bucket to a local path with the AWS CLI, using credentials read from a Kubernetes Secret.

    s3-download
    Changelog
    • v1.0.22026-08-11Move amazon/aws-cli from 2.36.14 to 2.36.20. Clears all 8 fixable OS advisories and the image scans clean again. The six patch releases in between carry service model updates only, and `aws s3 cp` out of a bucket was round-tripped against MinIO on both digests.
    • v1.0.12026-08-02Move amazon/aws-cli from 2.17.19 to 2.36.14. Clears all 90 fixable CRITICAL/HIGH; the image now scans clean.
    • v1.0.02026-07-16Initial release.
  • List objects under an S3 prefixv1.0.2Object storage

    List the objects under a prefix in an Amazon S3 bucket with the AWS CLI, using credentials read from a Kubernetes Secret.

    s3-list
    Changelog
    • v1.0.22026-08-11Move amazon/aws-cli from 2.36.14 to 2.36.20. Clears all 8 fixable OS advisories and the image scans clean again. The six patch releases in between carry service model updates only, and `aws s3 ls --recursive` was round-tripped against MinIO on both digests.
    • v1.0.12026-08-02Move amazon/aws-cli from 2.17.19 to 2.36.14. Clears all 90 fixable CRITICAL/HIGH; the image now scans clean.
    • v1.0.02026-07-16Initial release.
  • Upload a file to Azure Blob Storagev1.0.2Object storage

    Upload a local file or artifact to an Azure Blob Storage container with the az CLI, authenticating with a storage account key read from a Kubernetes Secret.

    azure-blob-upload
    Changelog
    • v1.0.22026-08-11Move azure-cli from 2.88.0 to 2.89.0. Fixable OS advisories drop from 25 to 8, and the 8 that stay are Azure Linux 3 packages only Microsoft can rebuild, recorded in hack/image-cve-exceptions.txt. 2.89.0 ships no storage changes at all, and `az storage blob upload --overwrite` was round-tripped against Azurite on both digests.
    • v1.0.12026-08-02Move azure-cli from 2.63.0 to 2.88.0. Fixable CRITICAL/HIGH drops from 103 to 30.
    • v1.0.02026-07-16Initial release.
  • Upload a file to Google Cloud Storagev1.0.4Object storage

    Upload a local file or artifact to a Google Cloud Storage bucket with gsutil, authenticating with a service-account key read from a Kubernetes Secret.

    gcs-upload
    Changelog
    • v1.0.42026-08-20Repin google/cloud-sdk:slim onto 581.0.0-slim, the digest :slim now heads at. gcloud goes 580.0.0 to 581.0.0 on the same Dockerfile: Entrypoint, Cmd, User and WorkingDir match across both digests and the only layers that differ are the ones carrying the version argument. The four util-linux advisories the old pin went red on, CVE-2026-53612 through CVE-2026-53615, are gone with Debian's 2.41.5-0+deb13u1, so the OS baseline record is deleted rather than rewritten. The eleven vendored advisories are the same eleven on both digests and keep their record.
    • v1.0.32026-08-11Repin google/cloud-sdk:slim on the current digest, which is also the newest 580.0.0-slim. gcloud goes 579.0.0 to 580.0.0 and gsutil stays at 5.37. The last fixable OS-package HIGH, linux-libc-dev CVE-2026-64561, is gone with the newer Debian trixie base, so the OS baseline record is deleted rather than rewritten. The three cryptography advisories in the bundled Python are unmoved and keep their record.
    • v1.0.22026-08-11Repin google/cloud-sdk:slim on the current digest. Same tag, newer build. Fixable OS-package HIGH drops from 21 to 1: the libexpat1 and linux-libc-dev updates have landed, one newer linux-libc-dev has not. gcloud goes 578.0.0 to 579.0.0 and gsutil stays at 5.37.
    • v1.0.12026-08-02Move google/cloud-sdk off the pinned 495.0.0-slim tag onto the rolling slim tag that bigquery-query already uses. Fixable CRITICAL/HIGH drops from 980 to 18. gcloud goes 495.0.0 to 578.0.0 and gsutil 5.30 to 5.37.
    • v1.0.02026-07-16Initial release.
  • Upload a file to S3v1.0.2Object storage

    Upload a local file or artifact to an Amazon S3 bucket with the AWS CLI, using credentials read from a Kubernetes Secret.

    s3-upload
    Changelog
    • v1.0.22026-08-11Move amazon/aws-cli from 2.36.14 to 2.36.20. Clears all 8 fixable OS advisories and the image scans clean again. The six patch releases in between carry service model updates only, and `aws s3 cp` into a bucket was round-tripped against MinIO on both digests.
    • v1.0.12026-08-02Move amazon/aws-cli from 2.17.19 to 2.36.14. Clears all 90 fixable CRITICAL/HIGH; the image now scans clean.
    • v1.0.02026-07-16Initial release.