Update default container config to avoid deprecation warning #18264
Conversation
This file contains hidden or 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
The default container config uses a deprecated setting which causes a warning when the container starts up. Use the updated setting to avoid the noise.
|
We need to do a bit more research in to the upgrade/compatability of this change. For example if |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Release notes
The default configuration for logstash container images no longer warns of a deprecated
http.hostconfiguration option.What does this PR do?
Use the
api.http.hostinstead ofhttp.postin the default container config to avoid noisy deprecation warnings.Why is it important/What is the impact to the user?
Consumers of container will not need to modify the default config to avoid seeing deprecation warnings.