Skip to content

Comments

[Security Solution][Detection Engine] fixes docs version reference in actions test#225611

Merged
delanni merged 2 commits intoelastic:mainfrom
vitaliidm:9_2/fixes-test-docs-version-reference
Jun 27, 2025
Merged

[Security Solution][Detection Engine] fixes docs version reference in actions test#225611
delanni merged 2 commits intoelastic:mainfrom
vitaliidm:9_2/fixes-test-docs-version-reference

Conversation

@vitaliidm
Copy link
Contributor

@vitaliidm vitaliidm commented Jun 27, 2025

Summary

We had a few cases of backport tests failing because version in docs link is hardcoded as current but can be previous version.

Examples:
#225582
#225584

Failed assertion:

Error: expected 'This rule's API key is unable to access all indices that match the ["host_alias"] pattern. To learn how to update and manage API keys, refer to https://www.elastic.co/guide/en/kibana/9.1/alerting-setup.html#alerting-authorization.\n\nThis rule is attempting to query data from Elasticsearch indices listed in the "Index patterns" section of the rule definition, however no index matching: ["host_alias"] was found. This warning will continue to appear until a matching index is created or this rule is disabled.' to contain 'This rule's API key is unable to access all indices that match the ["host_alias"] pattern. To learn how to update and manage API keys, refer to https://www.elastic.co/guide/en/kibana/current/alerting-setup.html#alerting-authorization.'

@vitaliidm vitaliidm added Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Detection Engine Security Solution Detection Engine Area backport:version Backport to applied version labels v9.1.0 v9.2.0 labels Jun 27, 2025
@vitaliidm vitaliidm self-assigned this Jun 27, 2025
@vitaliidm vitaliidm marked this pull request as ready for review June 27, 2025 10:49
@vitaliidm vitaliidm requested a review from a team as a code owner June 27, 2025 10:49
@vitaliidm vitaliidm requested a review from dhurley14 June 27, 2025 10:49
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detection-engine (Team:Detection Engine)

@vitaliidm vitaliidm added the release_note:skip Skip the PR/issue when compiling release notes label Jun 27, 2025
@vitaliidm vitaliidm enabled auto-merge (squash) June 27, 2025 14:15
@delanni delanni disabled auto-merge June 27, 2025 14:18
@delanni delanni merged commit fefaea7 into elastic:main Jun 27, 2025
10 of 12 checks passed
@kibanamachine
Copy link
Contributor

Starting backport for target branches: 9.1

https://github.com/elastic/kibana/actions/runs/15928520919

kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Jun 27, 2025
… actions test (elastic#225611)

## Summary

We had a few cases of backport tests failing because version in docs
link is hardcoded as `current` but can be previous version.

Examples:
elastic#225582
elastic#225584

Failed assertion:

> Error: expected 'This rule\'s API key is unable to access all indices
that match the ["host_alias"] pattern. To learn how to update and manage
API keys, refer to
https://www.elastic.co/guide/en/kibana/9.1/alerting-setup.html#alerting-authorization.\n\nThis
rule is attempting to query data from Elasticsearch indices listed in
the "Index patterns" section of the rule definition, however no index
matching: ["host_alias"] was found. This warning will continue to appear
until a matching index is created or this rule is disabled.' to contain
'This rule\'s API key is unable to access all indices that match the
["host_alias"] pattern. To learn how to update and manage API keys,
refer to
https://www.elastic.co/guide/en/kibana/current/alerting-setup.html#alerting-authorization.'

(cherry picked from commit fefaea7)
@kibanamachine
Copy link
Contributor

💚 All backports created successfully

Status Branch Result
9.1

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

@elasticmachine
Copy link
Contributor

💔 Build Failed

Failed CI Steps

History

cc @vitaliidm

delanni pushed a commit that referenced this pull request Jun 27, 2025
…nce in actions test (#225611) (#225648)

# Backport

This will backport the following commits from `main` to `9.1`:
- [[Security Solution][Detection Engine] fixes docs version reference in
actions test (#225611)](#225611)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Vitalii
Dmyterko","email":"92328789+vitaliidm@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-27T14:18:39Z","message":"[Security
Solution][Detection Engine] fixes docs version reference in actions test
(#225611)\n\n## Summary\n\nWe had a few cases of backport tests failing
because version in docs\nlink is hardcoded as `current` but can be
previous
version.\n\nExamples:\nhttps://github.com//pull/225582\nhttps://github.com//pull/225584\n\nFailed
assertion:\n\n> Error: expected 'This rule\\'s API key is unable to
access all indices\nthat match the [\"host_alias\"] pattern. To learn
how to update and manage\nAPI keys, refer
to\nhttps://www.elastic.co/guide/en/kibana/9.1/alerting-setup.html#alerting-authorization.\\n\\nThis\nrule
is attempting to query data from Elasticsearch indices listed in\nthe
\"Index patterns\" section of the rule definition, however no
index\nmatching: [\"host_alias\"] was found. This warning will continue
to appear\nuntil a matching index is created or this rule is disabled.'
to contain\n'This rule\\'s API key is unable to access all indices that
match the\n[\"host_alias\"] pattern. To learn how to update and manage
API keys,\nrefer
to\nhttps://www.elastic.co/guide/en/kibana/current/alerting-setup.html#alerting-authorization.'","sha":"fefaea74fa838c8eecdc24f6588f68e2fc25eebe","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:
SecuritySolution","Team:Detection
Engine","backport:version","v9.1.0","v9.2.0"],"title":"[Security
Solution][Detection Engine] fixes docs version reference in actions
test","number":225611,"url":"https://github.com/elastic/kibana/pull/225611","mergeCommit":{"message":"[Security
Solution][Detection Engine] fixes docs version reference in actions test
(#225611)\n\n## Summary\n\nWe had a few cases of backport tests failing
because version in docs\nlink is hardcoded as `current` but can be
previous
version.\n\nExamples:\nhttps://github.com//pull/225582\nhttps://github.com//pull/225584\n\nFailed
assertion:\n\n> Error: expected 'This rule\\'s API key is unable to
access all indices\nthat match the [\"host_alias\"] pattern. To learn
how to update and manage\nAPI keys, refer
to\nhttps://www.elastic.co/guide/en/kibana/9.1/alerting-setup.html#alerting-authorization.\\n\\nThis\nrule
is attempting to query data from Elasticsearch indices listed in\nthe
\"Index patterns\" section of the rule definition, however no
index\nmatching: [\"host_alias\"] was found. This warning will continue
to appear\nuntil a matching index is created or this rule is disabled.'
to contain\n'This rule\\'s API key is unable to access all indices that
match the\n[\"host_alias\"] pattern. To learn how to update and manage
API keys,\nrefer
to\nhttps://www.elastic.co/guide/en/kibana/current/alerting-setup.html#alerting-authorization.'","sha":"fefaea74fa838c8eecdc24f6588f68e2fc25eebe"}},"sourceBranch":"main","suggestedTargetBranches":["9.1"],"targetPullRequestStates":[{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/225611","number":225611,"mergeCommit":{"message":"[Security
Solution][Detection Engine] fixes docs version reference in actions test
(#225611)\n\n## Summary\n\nWe had a few cases of backport tests failing
because version in docs\nlink is hardcoded as `current` but can be
previous
version.\n\nExamples:\nhttps://github.com//pull/225582\nhttps://github.com//pull/225584\n\nFailed
assertion:\n\n> Error: expected 'This rule\\'s API key is unable to
access all indices\nthat match the [\"host_alias\"] pattern. To learn
how to update and manage\nAPI keys, refer
to\nhttps://www.elastic.co/guide/en/kibana/9.1/alerting-setup.html#alerting-authorization.\\n\\nThis\nrule
is attempting to query data from Elasticsearch indices listed in\nthe
\"Index patterns\" section of the rule definition, however no
index\nmatching: [\"host_alias\"] was found. This warning will continue
to appear\nuntil a matching index is created or this rule is disabled.'
to contain\n'This rule\\'s API key is unable to access all indices that
match the\n[\"host_alias\"] pattern. To learn how to update and manage
API keys,\nrefer
to\nhttps://www.elastic.co/guide/en/kibana/current/alerting-setup.html#alerting-authorization.'","sha":"fefaea74fa838c8eecdc24f6588f68e2fc25eebe"}}]}]
BACKPORT-->

Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com>
szaffarano pushed a commit to szaffarano/kibana that referenced this pull request Jun 27, 2025
… actions test (elastic#225611)

## Summary

We had a few cases of backport tests failing because version in docs
link is hardcoded as `current` but can be previous version.

Examples:
elastic#225582
elastic#225584

Failed assertion:

> Error: expected 'This rule\'s API key is unable to access all indices
that match the ["host_alias"] pattern. To learn how to update and manage
API keys, refer to
https://www.elastic.co/guide/en/kibana/9.1/alerting-setup.html#alerting-authorization.\n\nThis
rule is attempting to query data from Elasticsearch indices listed in
the "Index patterns" section of the rule definition, however no index
matching: ["host_alias"] was found. This warning will continue to appear
until a matching index is created or this rule is disabled.' to contain
'This rule\'s API key is unable to access all indices that match the
["host_alias"] pattern. To learn how to update and manage API keys,
refer to
https://www.elastic.co/guide/en/kibana/current/alerting-setup.html#alerting-authorization.'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:version Backport to applied version labels release_note:skip Skip the PR/issue when compiling release notes Team:Detection Engine Security Solution Detection Engine Area Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v9.1.0 v9.2.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants