Fix typo in ILM warning message#19819
Conversation
|
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
1 similar comment
|
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
💔 Tests FailedExpand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
|
Pinging @elastic/integrations (Team:Integrations) |
|
jenkins run the tests please |
(cherry picked from commit 9b7080f)
* upstream/master: [CI] support windows-2012 (elastic#19773) Do not update go.mod during packaging and testing (elastic#19823) Fix typo in ILM warning message (elastic#19819) [Winlogbeat] Remove beta tag from Powershell and Security modules (elastic#19817) feat: move the multibranch pipeline job to the beats repo (elastic#19698) Fix parsing timestamp in Filebeat registry tests (elastic#19796) Add text & flattened fields in aws cloudtrail fileset (elastic#19121)
What does this PR do?
It is a fix typo PR. It only adds a space for proper YAML in ILM warning message.
I ran
grep -lri 'setup.ilm.overwrite:true'in the repository root folder to find files where this typo could be and it only showed 1. So I think the issue #18100 could be closed.Why is it important?
If a user follows the instruction, it leads to an error because the YAML syntax is wrong in the message.
Closes #18100