Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.x] [Security Solution][Endpoint] Add FTR API tests that validates creation of DOT indices (#197899) #198561

Closed
wants to merge 5 commits into from

Conversation

paul-tavares
Copy link
Contributor

Backport

This will backport the following commits from main to 8.x:

Questions ?

Please refer to the Backport tool documentation

…on of DOT indices (elastic#197899)

## Summary

- Adds new FTR API test suite for validating that DOT indices are
created whenever a policy in fleet is created/updated
- Renamed and moved `DEFAULT_DIAGNOSTIC_INDEX` `const` to security
solution top-level `common` directory for better reuse
- Moved utility function that builds an index name with the `namespace`
included to top-level `common` directory for better reuse
- Created some additional scripting methods in the Fleet services module
for updating fleet policies

(cherry picked from commit a5d571a)

# Conflicts:
#	x-pack/plugins/security_solution/server/fleet_integration/handlers/create_policy_datastreams.ts
@elasticmachine
Copy link
Contributor

elasticmachine commented Nov 4, 2024

💔 Build Failed

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #46 / Endpoint Policy @ess @serverless @skipInServerlessMKI Creation of DOT indices for elastic defend policies should create indices when endpoint integration policy is created
  • [job] [logs] FTR Configs #46 / Endpoint Policy @ess @serverless @skipInServerlessMKI Creation of DOT indices for elastic defend policies should create indices when endpoint integration policy is created
  • [job] [logs] FTR Configs #60 / InfraOps App Logs UI Log Entry Categories Tab with a trial license Shows no data page when indices do not exist

Metrics [docs]

✅ unchanged

History

@paul-tavares
Copy link
Contributor Author

So it turns out that I really an't backport this change (the FTR tests) to 8.x due to the fact that the associated Elasticsearch change is not applied at the 8.x level. Closing

auto-merge was automatically disabled November 4, 2024 21:18

Pull request was closed

@paul-tavares paul-tavares deleted the backport/8.x/pr-197899 branch November 4, 2024 21:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants