Skip to content

v0.3.0

Choose a tag to compare

View all tags
@chrisdoehring chrisdoehring released this 08 Oct 16:46
· 68 commits to main since this release
v0.3.0
2f07702
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Highlights

Two behaviour changes agents and scripts should know about

  • observations search now requires exactly one of --subject-id, --source-id, --subjectsource-id, --sourceprovider-id, and defaults --since to 24 hours before --until (or before now). Without a selector, ER returned every observation on the site and the CLI paged through all of it. (#23)
  • events post validates each event's details against the type's schema as ER renders it before anything is sent: unknown fields, values outside a select's choices, wrong types, out-of-range numbers and missing required fields are reported one line each and nothing is posted. ER's API does not make these checks itself. --no-validate skips it. (#26, #27, #28)

New

  • events search --event-type takes event-type values and display names as well as ids, comma-mixed; names are resolved for you and an unknown name lists the server's values. (#29)
  • Every paginated read command answers to both list and search. featuresets list, spatial-features list|get and spatial-feature-groups get are new. (#23)
  • Reads retry transient failures (429, 5xx, connection and body-read errors) with 0/2/4 s backoff, announced on stderr; Retry-After is honoured up to 30 s. Writes are never replayed. (#30)
  • er --version. (#30)

Renamed

  • fences is now spatial-feature-groups. A spatial feature group holds roads, water points and boundaries as well as geofences, and nothing in ER is called a fence. No alias is kept. (#23)

What's Changed

  • Read surface: list/search aliases, featuresets list, fences -> spatial-feature-groups + spatial-features (#23)
  • Spec: record PR 23 decisions, close spec-derived flags as no, add Hardening section (#25)
  • events post: validate event details against the type's schema before sending (#26)
  • events post: reject explicit null event_details before posting (#27)
  • events post: refuse non-object event_details at load, independent of --no-validate (#28)
  • events search: --event-type accepts values and display names, resolved to ids (#29)
  • Reads retry transient failures with backoff; add --version (#30)
  • Bump version to 0.3.0 (#31)

Full Changelog: v0.2.0...v0.3.0

Assets 6
Loading