Skip to content

[receiver/fluentforward] move struct to internal, do not expose in API #39831

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

Merged
merged 1 commit into from
May 2, 2025

Conversation

atoulme
Copy link
Contributor

@atoulme atoulme commented May 2, 2025

This struct is internal to the receiver and not exposed as part of Config.

Copy link
Contributor

@codeboten codeboten left a comment

Choose a reason for hiding this comment

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

should this be documented as a breaking change?

@atoulme atoulme force-pushed the move_ack_to_internal branch from d8d6692 to c4e8611 Compare May 2, 2025 19:20
@atoulme
Copy link
Contributor Author

atoulme commented May 2, 2025

should this be documented as a breaking change?

I think this will bring more attention than is warranted to this change, but I guess we can.

@atoulme atoulme force-pushed the move_ack_to_internal branch from c4e8611 to 80fe570 Compare May 2, 2025 19:22
@atoulme atoulme changed the title [chore] move struct to internal, do not expose in API [receiver/fluentforward] move struct to internal, do not expose in API May 2, 2025
@atoulme
Copy link
Contributor Author

atoulme commented May 2, 2025

added a changelog.

@atoulme atoulme force-pushed the move_ack_to_internal branch from 80fe570 to 3df6c8b Compare May 2, 2025 21:03
@atoulme atoulme merged commit e0646e1 into open-telemetry:main May 2, 2025
173 checks passed
@github-actions github-actions bot added this to the next release milestone May 2, 2025
vincentfree pushed a commit to ing-bank/opentelemetry-collector-contrib that referenced this pull request May 6, 2025
open-telemetry#39831)

This struct is internal to the receiver and not exposed as part of
Config.

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
vincentfree pushed a commit to ing-bank/opentelemetry-collector-contrib that referenced this pull request May 20, 2025
open-telemetry#39831)

This struct is internal to the receiver and not exposed as part of
Config.

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
songy23 pushed a commit that referenced this pull request May 22, 2025
Adds a new check on checkapi that prevents the unkeyed initialization of
literals. Unkeyed initialization breaks if the API exposed by the struct
fields changes. Adding an anonymous _ struct{} field ensures all
developers must use a named initialization.

This is explained in more detail in
open-telemetry/opentelemetry-collector#12360

This PR needs #39830 and #39831 merged first.

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
dragonlord93 pushed a commit to dragonlord93/opentelemetry-collector-contrib that referenced this pull request May 23, 2025
open-telemetry#39831)

This struct is internal to the receiver and not exposed as part of
Config.

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
dragonlord93 pushed a commit to dragonlord93/opentelemetry-collector-contrib that referenced this pull request May 23, 2025
…ry#39832)

Adds a new check on checkapi that prevents the unkeyed initialization of
literals. Unkeyed initialization breaks if the API exposed by the struct
fields changes. Adding an anonymous _ struct{} field ensures all
developers must use a named initialization.

This is explained in more detail in
open-telemetry/opentelemetry-collector#12360

This PR needs open-telemetry#39830 and open-telemetry#39831 merged first.

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
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.

3 participants