The most important change is that otel-cli exec now treats arguments as an argv
list instead of munging them into a string. This shouldn't break anyone doing sensible
things, but could if folks were expecting the old sh -c behavior.
Envvars are no longer deleted before calling exec. Actually, they still are, but otel-cli
backs up its envvars early so they can be propagated anyways.
The rest of the visible changes are incremental additions or fixes. As for the invisible,
otel-cli now generates span protobufs directly, and no longer goes through the
opentelemetry-go SDK. This ended up making some code cleaner, aside from some of the
protobuf-isms that show up.
A user has a use case for setting custom trace and span ids, so the --force-trace-id
and --force-span-id options were added to span, exec, and other span-generating
subcommands.
Changelog
- c75e2bf add --force-trace-id and --force-span-id options (#173) (#210)
- 295888d add a demo that shows how to work around span background races (#168)
- f6a0c8e add tests, fix exec end timestamp (#189) (#195)
- 0f61b87 allow setting status code and description at the end of background spans #197 (#201)
- 43f8dd9 chore(deps): update actions/setup-go action to v4 (#177)
- 9706378 chore(deps): update jaegertracing/all-in-one docker tag to v1.44.0 (#184)
- 3e7501a chore(deps): update otel/opentelemetry-collector docker tag to v0.76.1 (#187)
- 7565b2c create spans directly using protobuf structures (#175)
- 0218730 documentation updates (#215)
- e672421 feat(windows/exec): Spawn powershell to run Windows commands (#179)
- f47323e fix config for the otel error handler (#199)
- 2060787 fix endpoint paths and signal-specific behavior (#200) (#214)
- 6fa50fc fix(deps): update module github.com/pterm/pterm to v0.12.59 (#185)
- e0426f8 fix(deps): update module github.com/pterm/pterm to v0.12.60 (#204)
- b3e146d make exec arg handling precise (#191) (#202)
- 25c2241 spring cleaning (#198)
- 8f9f2f5 update dependencies (#211)
- fcc3825 work around otel reading envvars #181 (#208)