From aa5834ef45fd1e69cc9372e9509d2768f2d34f74 Mon Sep 17 00:00:00 2001 From: Sam Catlow Date: Sun, 4 Oct 2026 03:10:23 +1100 Subject: [PATCH] refactor(examples): the firewall workflow moves to archipelago --- README.md | 5 ++-- docker-compose.yml | 2 +- examples/workflows/firewall-contain.yaml | 27 -------------------- examples/workflows/firewall-investigate.yaml | 25 ------------------ 4 files changed, 3 insertions(+), 56 deletions(-) delete mode 100644 examples/workflows/firewall-contain.yaml delete mode 100644 examples/workflows/firewall-investigate.yaml diff --git a/README.md b/README.md index 450eb1470..3b5f90511 100644 --- a/README.md +++ b/README.md @@ -73,9 +73,8 @@ Workflows can also call other workflows and pass data between them. Each called workflow has its own run and agent profile. A caller can wait for the result or continue while the called workflow runs independently. -See the -[firewall investigation example](examples/workflows/firewall-investigate.yaml) -for a workflow that uses typed inputs, a network investigator profile, and no +The archipelago marketplace's `workflows/firewall` package is an example of a +workflow that uses typed inputs, a network investigator profile, and no repository. ## Identities and controlled execution diff --git a/docker-compose.yml b/docker-compose.yml index 39bc4c7f8..c2deac2be 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -85,7 +85,7 @@ services: # ── example agent profile image ───────────────────────────────────── # The agent image plus network lookup tools, for a workflow that names - # `profile: network-investigator` (examples/workflows/firewall-investigate.yaml). + # `profile: network-investigator` (archipelago: workflows/firewall). # Build-only for the same reason as agent. It is local, so leave # containers.pull_policy at "missing": "always" would try to pull it. agent-net: diff --git a/examples/workflows/firewall-contain.yaml b/examples/workflows/firewall-contain.yaml deleted file mode 100644 index 7a8fd8c6e..000000000 --- a/examples/workflows/firewall-contain.yaml +++ /dev/null @@ -1,27 +0,0 @@ -# The containment workflow a firewall-investigate run calls: -# firewall-investigate (workflow.call, wait: true) hands its findings upward -# from its declared summary, and this workflow's own agent stage decides and -# records the containment as its own declared outputs. Paste it into the -# dashboard's workflow definitions alongside firewall-investigate. -id: firewall-contain -repository: none -profile: network-investigator -inputs: - src_ip: { type: string, required: true } -outputs: - contained: { type: bool, required: true } - summary: { type: string } -steps: - - type: workflow.call - settings: - workflow: firewall-investigate - wait: true - inputs: { src_ip: "inputs.src_ip" } - outputs: { summary: "outputs.summary" } - - type: agent.run - settings: - mission: >- - Using the investigation summary the called workflow returned, decide - whether the source address in the inputs should be contained. Write - your decision with the contained tool, and a one-line rationale with - the summary tool. \ No newline at end of file diff --git a/examples/workflows/firewall-investigate.yaml b/examples/workflows/firewall-investigate.yaml deleted file mode 100644 index dbe799a53..000000000 --- a/examples/workflows/firewall-investigate.yaml +++ /dev/null @@ -1,25 +0,0 @@ -# A workflow with no repository: a binding on a firewall event type assigns -# src_ip from a mapped parameter and runs one agent mission in a scratch -# workspace under the network-investigator profile. Paste it into the -# dashboard's workflow definitions. -# -# Its declared output (summary) is offered to the agent stages as a capture -# tool named after it; a wait:true caller publishes it as one of its own -# outputs. -id: firewall-investigate -repository: none -profile: network-investigator -inputs: - src_ip: { type: string, required: true } - severity: { type: string } -outputs: - summary: { type: string } -steps: - - type: agent.run - settings: - mission: >- - Investigate the source address in the inputs: who owns it, what it - resolves to, and whether it is reachable. Report what you found and - how serious it looks given the severity, and write your one-line - conclusion with the summary tool. - read_only: true