[8.2](backport #1299) Always add api_key to Elasticsearch output
#1306
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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
This fixes a few issues: - When the hash on the permission and the hash on the agent were the same the key were not added to the output. This was causing the agent to not be able to connect to Elasticsearch. If you changes an integration policy field, like the host, and the data stream are the same the permission hash will stay the same. - Fix a possible issue when the new key was not saved on the Agent model, the key was only saved when we were targetting a default agent policy. Currently we only support a single ES output so this should always be saved. - Reorganize the test to ensure that all the scenario from the case statement are tested. Fix: elastic/elastic-agent#285 (cherry picked from commit 372e598)
(cherry picked from commit 681be39)
(cherry picked from commit 96ccfaa)
(cherry picked from commit 6b7f21f)
💔 Build Failed
Expand to view the summary
Build stats
Test stats 🧪
Steps errors
Expand to view the steps failures
|
|
/test |
|
Merging this same flaky test as #1289 |
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.
This is an automatic backport of pull request #1299 done by Mergify.
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com