Skip to content

fix: align jaeger tracing flag names#27407

Open
ivanov17andrey wants to merge 1 commit into
influxdata:mainfrom
ivanov17andrey:codex/fix-jaeger-tracing-flags
Open

fix: align jaeger tracing flag names#27407
ivanov17andrey wants to merge 1 commit into
influxdata:mainfrom
ivanov17andrey:codex/fix-jaeger-tracing-flags

Conversation

@ivanov17andrey

@ivanov17andrey ivanov17andrey commented May 7, 2026

Copy link
Copy Markdown

Closes #27406

Align the canonical Jaeger debug-name and tags flags with the rest of the
--traces-exporter-jaeger-* family (and with their env var names), while
keeping the previous shorter names as backwards-compatible aliases.

Changes

  • Rename --traces-jaeger-debug-name--traces-exporter-jaeger-debug-name
    (alias kept) in core/trace_exporters/src/lib.rs.
  • Rename --traces-jaeger-tags--traces-exporter-jaeger-tags
    (alias kept) in core/trace_exporters/src/lib.rs.
  • Update the packaged influxdb3-core.conf, the serve_all.txt help text,
    and the launcher TOML→env mapping in influxdb3-launcher so the new
    canonical names are first-class while legacy spellings still resolve.
  • Update the non-sensitive parameter categorization in
    influxdb3/src/commands/serve/cli_params.rs.
  • Add unit tests covering both the new flag→env mapping and the deprecated
    flag aliases continuing to parse.

Tests

  • cargo nextest run --workspace

  • cargo clippy --all-targets --workspace -- -D warnings

  • cargo fmt --all

  • python3 -m py_compile .circleci/packages/influxdb3/fs/usr/lib/influxdb3/influxdb3-launcher

  • git diff --check

  • I've read the contributing section of the project README.

  • Signed CLA (if not already signed).

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.

Inconsistent CLI flag vs env var: --traces-jaeger-{debug-name,tags} drop EXPORTER but env keeps it

1 participant