Move away from deprecated container input #8455
Merged
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
|
buildkite test this -f p=gke,t=TestBeatSecureSettings -m s=7.17.26,s=8.18.0-SNAPSHOT,s=9.0.0-SNAPSHOT |
kvalliyurnatt
approved these changes
Feb 3, 2025
pebrc
added a commit
that referenced
this pull request
Feb 6, 2025
…8456) Follow up to #8455 Replaces all the references to the container input type with the new syntax based on filestream taken from elastic/beats#36950 I will follow up on the e2e monitoring config in a separate PR.
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.
Another test failure in stack 9.0
My theory is that that we are using depracated input that makes this test fail.
This updates to the new recommended way based on elastic/beats#36950
We probably also have to check our config examples.