generated from coulomb/repo-seed
Add automation inventory surface
This commit is contained in:
@@ -136,6 +136,36 @@ The response reports:
|
||||
- `schedules.deleted_orphans`
|
||||
- bounded `errors[]`
|
||||
|
||||
## Automation inventory
|
||||
|
||||
Use the repo-native inventory command to answer "what automations are scheduled
|
||||
at all?" before checking whether a recent window succeeded. The command is
|
||||
read-only: it loads ActivityDefinition rows or files and, when `TEMPORAL_HOST`
|
||||
is configured, describes Temporal schedules for visibility. It does not sync,
|
||||
upsert, pause, delete, or enqueue schedules.
|
||||
|
||||
```bash
|
||||
# Human-readable configured automation inventory.
|
||||
make automation-list
|
||||
|
||||
# JSON for scripts or assistant summarization.
|
||||
make automation-list-json
|
||||
|
||||
# Common filters.
|
||||
make automation-list ENABLED=true TRIGGER=cron
|
||||
make automation-list ACTIVITY_ID=6fca51fa-387a-4fd0-bc4e-d62c29eb859a
|
||||
```
|
||||
|
||||
Inventory answers what is configured; `make automation-status` answers what
|
||||
happened in a time window. Missing optional live sources are warnings, not
|
||||
silent omissions, so a degraded local run still lists repo definition files.
|
||||
|
||||
Compact human output looks like:
|
||||
|
||||
```text
|
||||
- Daily State Hub WSJF Triage [enabled cron] schedule=activity-schedule-... trigger=20 7 * * * tz=Europe/Berlin source=files temporal=not_checked
|
||||
```
|
||||
|
||||
## Automation status
|
||||
|
||||
Use the repo-native status command to answer operator questions such as "how did
|
||||
|
||||
Reference in New Issue
Block a user