onboarding_config_draft
Read-only
[READ][risk=low] The config.yaml endpoints a stored scan can justify.
Instructions
[READ][risk=low] The config.yaml endpoints a stored scan can justify.
Closes the gap where a site scanned forty devices and then retyped all forty
by hand. Reads a stored scan; writes nothing. `config.yaml` is edited by a
person, exactly as with `iaiops tags apply`.
**Every drafted field says whether the scan established it.** A field with
`value: null` was NOT established, and its `caution` says what it is waiting
for — do not fill one in and do not drop it. Dropping it lets the protocol
default apply in silence, which is how a Modbus gateway gets read at unit 1
and shows a confident number for the wrong machine. Carry the cautions to
whoever merges this; they are the content, not decoration.
**Only CONFIRMED protocols become endpoints.** An open port means something
is listening, not that it speaks the protocol; those hosts appear under
`skipped` with the reason. `limits` states what this draft structurally
cannot contain — a protocol's absence here is not evidence of its absence at
the site.
`tags` is always empty and this tool will not fill it. A scan finds devices;
which point means run state or good count is process knowledge, and a wrong
production counter yields a plausible OEE, which is worse than an error
(D16). That confirmation is a person's, via `iaiops tags export` / `apply`.
`scan_id` empty means the newest stored scan. `db` overrides the store
(.db/.sqlite, under $IAIOPS_HOME, the config dir or an IAIOPS_AGENT_READ_DIRS dir).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| db | No | ||
| scan_id | No |