Skip to main content
← Back to list
01Issue
BugShippedSwamp CLIPublic
Assigneeszack

Relationships

#4495 swamp workflow validate fails a repo because of a pulled extension's bundled workflow (@keeb/setup-docker resolves fleet against the repo's own behavior)

Opened by ascandroli · 11/7/2026· Shipped 11/7/2026

What happens

A bare swamp workflow validate validates the workflows bundled in pulled extensions alongside the repo's own, and it resolves their modelIdOrName against the repo's behavior instances. A bundled workflow's instance names are the extension author's examples, so they collide with whatever the consuming repo happens to call its behaviors.

@keeb/docker (2026.07.18.1 and the latest, 2026.10.15.2) bundles @keeb/setup-docker, whose step lookup calls fleet.lookup. A repo with its own behavior named fleet, of type @swamp/ssh (no lookup method), fails:

@keeb/setup-docker
  ⚠ Step inputs for 'auth' in job 'setup' (keebDev02.auth) (behavior not found)
    → Behavior instance not found — may be created at runtime, or could be a typo
  ✗ Step inputs for 'lookup' in job 'setup' (fleet.lookup)
    → Method 'lookup' not found on behavior type '@swamp/ssh'
  ⚠ Step inputs for 'install-docker' in job 'setup' (dockerEngine.install) (behavior not found)
    → Behavior instance not found — may be created at runtime, or could be a typo
Result: FAILED

Summary: 0/1 workflows passed, 2 warning(s)
Overall: FAILED

In our real repo all of our own workflows pass (10/11); only the bundled one fails. A repo with no behavior named fleet sees only the two warnings.

Repro (fresh repo)

  1. swamp repo init
  2. swamp extension pull @keeb/docker
  3. swamp behavior create @swamp/ssh fleet (any type without a lookup method)
  4. swamp workflow validate → Overall: FAILED on @keeb/setup-docker

swamp 20261027.195148.0-sha.6baee087 on macOS (Darwin 24.6.0); also seen on Linux with earlier builds.

What would help (any one)

  • Leave pulled-extension workflows out of a bare swamp workflow validate, or add a flag such as --local-only, so CI can validate only the repo's own workflows.
  • Treat an unresolved or mismatched instance reference inside a pulled workflow as a warning, not an error: those names are placeholders until the user wires the workflow up.
  • Let swamp extension pull / install skip an extension's bundled workflows when only its behavior types are wanted.

Workaround in use

CI runs swamp workflow validate <name> once per file under workflows/.


Note for the @keeb/docker author (separate, optional): setup-docker hard-codes keebDev02, fleet and dockerEngine, instance names from the author's own setup. Taking them as workflow inputs would make it portable.

02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 17 MOREPR_LINKED+ 2 MORESESSION_SUMMARIZED

Shipped

11/7/2026, 3:18:55 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
zack assigned zack11/7/2026, 1:26:27 PM
Editable. Press Enter to edit.

zack commented 11/7/2026, 3:18:56 PM

Thanks @ascandroli for reporting this! We shipped: A bare swamp workflow validate checks only the workflows the repo authors (workflows/, extensions/workflows and local extension source dirs) and skips the workflows bundled in pulled extensions under the pulled-extensions root, whose instance names are the extension author's placeholders. It reports how many it skipped (a log line after the summary, pulledWorkflowsSkipped in JSON). Naming a pulled workflow still validates it, and nested-workflow references still resolve against the full composite repository. The CLI and the serve workflow.validate handler change together so remote and local results agree.. The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

Sign in to post a ripple.