elastic
[Scout] update configs discovery based on .meta info
Summary
Summarize your PR. If it involves visual changes include a screenshot or gif.
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
- [ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
- [ ] Documentation was added for features that require explanation or tutorials
- [ ] Unit or functional tests were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
- [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The
release_note:breakinglabel should be applied in these situations. - [ ] Flaky Test Runner was used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section, and the correct
release_note:*label is applied per the guidelines - [ ] Review the backport guidelines and apply applicable
backport:*labels.
Identify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.
- [ ] See some risk examples
- [ ] ...
:hourglass_flowing_sand: Build in-progress, with failures
- Buildkite Build
- Commit: 590329f53d3dde7341903e05d9f8c3d4e19dc64a
Failed CI Steps
Test Failures
- [job] [logs] FTR Configs #85 / Agent Builder converse Conversation Error Handling shows error message when there is an error and allows user to retry
- [job] [logs] FTR Configs #120 / Package policies Package Policy - input package behavior should not have created any ES assets on install
- [job] [logs] FTR Configs #120 / Package policies Package Policy - input package behavior should not have created any ES assets on install
History
- :broken_heart: Build #373244 failed bf1686c789fc290b13777eb7d947a7b728c26fc2
- :green_heart: Build #372886 succeeded 88699b85b8900c37a48622435fd55b548c014f04
- :yellow_heart: Build #372713 was flaky 83116e75415121273d2d7beea1e5dc398f3f050d
- :broken_heart: Build #372283 failed 54a7bd5a1e70feb8db2bfb64c3d20f615ad622d9
- :yellow_heart: Build #372006 was flaky b09650ee436d670cf19f860984797b66f1184583
- :yellow_heart: Build #371236 was flaky 2ac61fdd611e0d330cad67de011efe8a1565e1df
cc @dmlemeshko
Starting backport for target branches: 8.19, 9.1, 9.2
https://github.com/elastic/kibana/actions/runs/20261130096
💔 All backports failed
| Status | Branch | Result |
|---|---|---|
| ❌ | 8.19 | Backport failed because of merge conflicts You might need to backport the following PRs to 8.19: - Add support for essentials and ease tiers in Scout (#244553) |
| ❌ | 9.1 | Backport failed because of merge conflicts |
| ❌ | 9.2 | Backport failed because of merge conflicts |
Manual backport
To create the backport manually run:
node scripts/backport --pr 245657
Questions ?
Please refer to the Backport tool documentation
💚 All backports created successfully
| Status | Branch | Result |
|---|---|---|
| ✅ | 9.2 |  |
Note: Successful backport PRs will be merged automatically after passing CI.
Questions ?
Please refer to the Backport tool documentation
💚 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
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. cc: @dmlemeshko
💚 All backports created successfully
| Status | Branch | Result |
|---|---|---|
| ✅ | 8.19 |  |
Note: Successful backport PRs will be merged automatically after passing CI.
Questions ?
Please refer to the Backport tool documentation