This repository has been archived by the owner on Sep 17, 2024. It is now read-only.
[7.15.x](backport #1644) feat: support running kibana with different configs #1661
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
* chore: match elastic-package's kibana config * chore: bring back kibana's configuration file This will enable having multiple config files per test suite, using the profile abstraction: one dir per config with the profile name * chore: rename configurations to default It will represent the default profile * chore: make kibana profile configurable Default profile will be 'default' * feat: support bootstrapping the stack with a new kibana config The bootstrap method is called before the test suite (only once) AND before each test scenario, as it has been defined as a Background clause. If an scenario wants to configure a new config file for Kibana, a new profile file with the new kibana config must be created at the compose level, using the ProfileName as directory name. * feat: create an on-the-fly elastic-package's profile from compose * chore: override default kibana config for elastic-package * fix: remove unused code * docs: document kibana config and profiles * chore: add a profile for preconfgured-policies * elas * chore: add placeholder for preconfigured policies * chore: support passing custom kibana ref to elastic-package * fix: honour current env Instead of replacing it, we want to append! * chore: unit test that we are not overriding the env (cherry picked from commit a207500)
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errors
Expand to view the tests failures
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automatic backport of pull request #1644 done by Mergify.
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.io/