attune-system/attune
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

working out the worker/execution interface

Browse Source
This commit is contained in:
David Culbreth
2026-02-08 12:55:33 -06:00
parent c62f41669d
commit a74e13fa0b
108 changed files with 21162 additions and 674 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/sensors/sensor-interface.md
View File

@@ -61,11 +61,17 @@ Sensors MUST accept the following environment variables:
|----------|----------|-------------|---------|
| `ATTUNE_API_URL` | Yes | Base URL of Attune API | `http://localhost:8080` |
| `ATTUNE_API_TOKEN` | Yes | Transient API token for authentication | `sensor_abc123...` |
| `ATTUNE_SENSOR_ID` | Yes | Sensor database ID | `42` |
| `ATTUNE_SENSOR_REF` | Yes | Reference name of this sensor | `core.timer` |
| `ATTUNE_MQ_URL` | Yes | RabbitMQ connection URL | `amqp://localhost:5672` |
| `ATTUNE_MQ_EXCHANGE` | No | RabbitMQ exchange name | `attune` (default) |
| `ATTUNE_LOG_LEVEL` | No | Logging verbosity | `info` (default) |
**Note:** These environment variables provide parity with action execution context (see `QUICKREF-execution-environment.md`). Sensors receive:
- `ATTUNE_SENSOR_ID` - analogous to `ATTUNE_EXEC_ID` for actions
- `ATTUNE_SENSOR_REF` - analogous to `ATTUNE_ACTION` for actions
- `ATTUNE_API_TOKEN` and `ATTUNE_API_URL` - same as actions for API access
### Alternative: stdin Configuration
For containerized or orchestrated deployments, sensors MAY accept configuration as JSON on stdin: