[exporter/datadog] Modify deprecation messages to reflect new plan #9422
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
KSerrania
approved these changes
Apr 25, 2022
mx-psi
added
the
ready to merge
|
Marking as 'ready to merge' since it has a codeowner approval. |
|
Changelog conflict resolved. |
bogdandrutu
approved these changes
Apr 25, 2022
djaglowski
pushed a commit
to djaglowski/opentelemetry-collector-contrib
that referenced
this pull request
May 10, 2022
…pen-telemetry#9422) * [exporter/datadog] Modify deprecation messages to reflect new plan * Add CHANGELOG entry * Capitalize changelog note Co-authored-by: Juraci Paixão Kröhling <juraci@kroehling.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Modifies deprecation messages to be less specific.
Originally, we intended to remove deprecated settings/functionality in a staggered fashion, but we have decided to do them all at once in a future minor version. Because of this, the logs need to be modified to be less specific and state that the features will be removed on a given version 'or later'. Mentioning a specific version is still useful for end-users to understand that the feature won't be removed at least until that point.
Link to tracking Issue: #8372