0.2.0
- Jobs queued by
Dandelion.PubSub.publish/3andDandelion.Queue.Ordered.insert/2carry the current OpenTelemetry trace context (W3Ctraceparent, in the job'smeta), so withopentelemetry_obana job's span is part of the trace of the code that queued it, on whichever node runs it. Nothing changes without OpenTelemetry. (opentelemetry_apiis an optional dependency.) Dandelion.Queue.Ordered.insert/2keeps the job's existingmeta(it used to replace it with the key).mix dandelion.gen.domain DOMAIN RESOURCE field:type …adds a resource to a project's domain in the project's own layout: model, repo, service, handler, JSON, migration, tests and the routes. The routes go through the project's:authenticatedpipeline when it has one.
The example and the generator (dandelion_new 0.2.0) also gain, in generated
projects: logins with signed tokens and per-user orders, /metrics, OpenTelemetry
tracing (Jaeger in the compose file), a network-partition proof, and orders priced
from a products table. Generated projects require dandelion ~> 0.2.0.
0.1.1
Dandelion.Cache.fetch/2emits[:dandelion, :cache, :fetch](result: :hit | :miss) for a hit/miss counter.
0.1.0
The first release: Dandelion.Cluster, Dandelion.Cache, Dandelion.Queue,
Dandelion.Queue.Ordered, Dandelion.PubSub and Dandelion.Migration,
extracted from the example service.