Skip to content

feat(config)!: replace device_specific/output_specific with type blocks - #14

Merged
dombyte merged 1 commit into
mainfrom
feat/config-type-blocks
Oct 15, 2026
Merged

dombyte merged 1 commit into
mainfrom
feat/config-type-blocks

Conversation

@dombyte

@dombyte dombyte commented Oct 15, 2026

Copy link
Copy Markdown
Owner

The settings of a device or output type now sit in a block named after the type, directly on the device or output:

- name: db
  type: influxdb
  influxdb:
    address: "http://influxdb:8181"
    batch_size: 5000
  • device_specific: / output_specific: are gone; modbus:, http:, influxdb:, mqtt:, csv:, api: move up one level.
  • batch_size, batch_timeout, max_retries, retry_delay move from the output into influxdb: (they only ever applied to InfluxDB).
  • Validation requires the block of the type and rejects a block of another type (it was ignored silently before).
  • example/config.yaml, README ("Upgrading from v1") and AGENTS.md updated.

Breaking: every existing config needs the migration shown in the README; next release is v2.0.0. Prepares the upcoming webhook output, which gets its own retry options in its own block.

The settings of a device or output type now sit in a block named after the
type, directly on the device or output (modbus:, http:, influxdb:, mqtt:,
csv:, api:). Validation requires the block of the type and rejects a block
of another type, which was ignored silently before.

The InfluxDB options batch_size, batch_timeout, max_retries and
retry_delay move from the output into the influxdb block.

BREAKING CHANGE: configs must drop the device_specific/output_specific
level and move the InfluxDB batch and retry options into influxdb:; see
"Upgrading from v1" in the README.
@dombyte
dombyte merged commit 60b8c56 into main Oct 15, 2026
3 checks passed
@dombyte
dombyte deleted the feat/config-type-blocks branch October 15, 2026 08:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant