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

[receiver/zipkin] move global server configuration parameters to a separate parameter #35851

Open
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

odubajDT
Copy link
Contributor

@odubajDT odubajDT commented Oct 17, 2024

Description

Move global server configuration parameters to a separate parameter under protocols parameter to allow future support of different protocols (like UDP), more context here

Link to tracking issue

Fixes #35730

Testing

Documentation

@github-actions github-actions bot added the receiver/zipkin Zipkin receiver label Oct 17, 2024
@odubajDT odubajDT changed the title [receiver/zipkin] move global server configuration parameters to a se… [receiver/zipkin] move global server configuration parameters to a separate parameter Oct 17, 2024
@odubajDT odubajDT marked this pull request as ready for review October 17, 2024 13:04
@odubajDT odubajDT requested a review from a team as a code owner October 17, 2024 13:04
@odubajDT
Copy link
Contributor Author

@andrzej-stencel would you please have time for a review?

# Use this changelog template to create an entry for release notes.

# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
change_type: breaking
Copy link
Member

@andrzej-stencel andrzej-stencel Nov 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you explain why marking this as a breaking change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's changing the configuration of the receiver even if it's changed behind a feature gate, but the user will be affected if the feature gate will be turned on/off. Do you consider this more as a deprecation?

odubajDT and others added 9 commits November 14, 2024 08:59
Signed-off-by: odubajDT <[email protected]>
Signed-off-by: odubajDT <[email protected]>
Signed-off-by: odubajDT <[email protected]>
Signed-off-by: odubajDT <[email protected]>
Signed-off-by: odubajDT <[email protected]>
Signed-off-by: odubajDT <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Refactor Zipkin Receiver to include Protocols in Config
3 participants