Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(opentelemetry): tostring header_type avoid concatenation nil error in log #13612

Draft
wants to merge 1 commit into
base: release/3.4.x
Choose a base branch
from

Conversation

tzssangglass
Copy link
Member

This is a backport of the https://github.com/Kong/kong-ee/pull/10137

Summary

The require of header_type is false, so the consumer can choose header_type to be nil in Kong Manager; if this is, Kong Manager would pass json.null to Kong, header_type could be nil in this case.

This PR respects this behavior and handles concatenation nil error when header_type is nil.

Checklist

  • The Pull Request has tests
  • A changelog file has been added to CHANGELOG/unreleased/kong or adding skip-changelog label on PR if unnecessary. README.md
  • The Pull Request has backports to all the versions it needs to cover
  • There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Issue reference

Fix: FTI-6119

…ror in log (#10137)

The require of header_type is false, so the consumer can choose `header_type` to be nil in Kong Manager; if this is, Kong Manager would pass `json.null` to Kong, `header_type` could be nil in this case.

This PR respects this behavior and handles concatenation nil error when `header_type` is nil.

Note that this is a fix that only exists in the 3.4 series.

Fix: [FTI-6119](https://konghq.atlassian.net/browse/FTI-6119)

Signed-off-by: tzssangglass <[email protected]>
@github-actions github-actions bot added core/tracing core/wasm Everything relevant to [proxy-]wasm labels Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core/tracing core/wasm Everything relevant to [proxy-]wasm size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant