Skip to content

[FTR] Split config listing for serverless projects#170973

Closed
pheyos wants to merge 3 commits intoelastic:mainfrom
pheyos:split_ftr_config_listing
Closed

[FTR] Split config listing for serverless projects#170973
pheyos wants to merge 3 commits intoelastic:mainfrom
pheyos:split_ftr_config_listing

Conversation

@pheyos
Copy link
Member

@pheyos pheyos commented Nov 9, 2023

Summary

This PR splits the FTR config listing so we have separate entries for stateful confgs as well as configs per serverless project type.

Why do we need this?

  • When running serverless tests on MKI, we don't use the local env setup that's defined in the configs files.
  • Instead, we already have a project running and need to point tests to it.
  • As a result, we need to know the list of configs that are suitable for each serverless project type

Change details

  • The .buildkite/ftr_configs.yml config listing no longer has an enabled key
  • Instead, it now has the keys enabled_stateful, enabled_serverless_search, enabled_serverless_security and enabled_serverless_observability
  • Existing test configs have been moved to their corresponding new key
  • Scripts that are reading the config listing have been adjusted accordingly

@pheyos pheyos added release_note:skip Skip the PR/issue when compiling release notes backport:skip This PR does not require backporting v8.12.0 labels Nov 9, 2023
@pheyos pheyos self-assigned this Nov 9, 2023
@kibana-ci
Copy link

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @pheyos

@pheyos
Copy link
Member Author

pheyos commented Aug 22, 2024

Actually done in #187440

@pheyos pheyos closed this Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting release_note:skip Skip the PR/issue when compiling release notes v8.12.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants