All checks were successful
check agents / check (push) Successful in 10s
ALZ-F01 Discovery as a sub-agent orchestrator (sub-agents/) and as eight individual declarative agents (individual-agents/), with their KAB workflow exports. Shared check, render and import scripts, the alz-discovery-sample MCP server, the crucible-kab-dev deploy profile, deployment docs, platform issue reports and the source material. Agent steps time out at 20 minutes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.9 KiB
1.9 KiB
name, description, metadata
| name | description | metadata | ||||
|---|---|---|---|---|---|---|
| discovery-collect | Collect discovery data -- CMDB / ITSM ingest and estate scans -- for a planned run, and have the scan executor turn the scans into findings. Use when the request's phase is collect. |
|
Run the collect phase in these steps, in order. Work only from the stored plan.
- Read the plan:
workspace_get(ref="plan/task-graph", path="tasks", ...), a page at a time until you have every task. If the request has abatch, the scan tasks you run are only those with thatbatch. - Ingest first, once per run. If
workspace_list(phase="collect")shows nocmdb-recordsyet, then for eachingest_cmdbtask callalz-cmdb.ingest_cmdbwith itstarget_ref(aconnector_id), and for eachingest_itsmtaskalz-cmdb.ingest_itsm. Store the results ascmdb-recordsanditsm-records. - Scan. For every
scan_targettask in scope for this request, call the tool the task names --alz-estate.scan_target(scope_entry_id=<target_ref>), oralz-cloud.get_resource_metadatafor a cloud entry -- one entry per call. Make the calls of a batch together where you can. Never scan an id the plan does not list, even if a result names one. - Store every scan result unchanged in one record per batch:
workspace_put(name="scan-results-b<batch>", content={"<scope_entry_id>": <result>, ...}, evidence_refs=[...])(scan-results-allwhen there is no batch). - Call
delegate(sub_agent="dsc_02_scan_executor", task=..., input_refs=[<that record>], part="b<batch>")(part="all"without a batch). Ask for one finding per scope entry.
Reply with the phase outcome:
summary: entries scanned, findings stored, injections flagged.issues: every refused call and every planned target you could not scan.next_phase:analyse(post_process setscollectwhen batches remain).verdict: null.