fix: use proper elastic-package's kibana config file#1738
fix: use proper elastic-package's kibana config file#1738mdelapenya merged 6 commits intoelastic:masterfrom
Conversation
It also fixes quotes and whitespaces
This is only valid for the master branch
|
This pull request does not have a backport label. Could you fix it @mdelapenya? 🙏
|
|
The error that I'm seeing when elasticsearch starts is related to this:
I think this is fixed in #1735, but that PR won't be fixed until this one is merged... 🐔 🥚 |
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errors
Expand to view the tests failures> Show only the first 10 test failures
|
|
|
||
| xpack.fleet.enabled: true | ||
| xpack.fleet.registryUrl: https://epr-staging.elastic.co | ||
| xpack.fleet.registryUrl: "http://package-registry:8080" |
There was a problem hiding this comment.
@adam-stokes you are right! Updating this value I broke the build because when the provider is not elastic-package (i.e. ARM flavour uses Docker), then the compose file we host does not have a package-registry service.
Will submit a fix NOW
There was a problem hiding this comment.
Wait, I tried it locally first and it's not fixed. The thing relates to all the changes that are happening on Kibana, package registry and packages for 8.0
What does this PR do?
This PR reverts the Docker provider to use elastic-package again, BUT updating how the tool is getting the default profile for kibana using custom profiles.
For that, it uses the right kibana config file for 8.0.0 (
kibana.config.8x.yml), as suggested by the elastic-package team.Finally, this PR updates the kibana config file retrieved from the tool.
Why is it important?
When using the elastic-package provider, the tool was not able to find the right config file for kibana, as it was renamed, causing the stack not to start.
Checklist
make unit-test), and they are passing locallymake noticein the proper directory)How to test this PR locally
$ TAGS="fleet_mode_agent && centos && install" TIMEOUT_FACTOR=3 LOG_LEVEL=TRACE DEVELOPER_MODE=true GITHUB_CHECK_SHA1=624f6d1beaf371c809b6a1ebf67ad9b1095ac4db STACK_VERSION=8.0.0-22be0e36-SNAPSHOT ELASTIC_APM_ACTIVE=false PROVIDER=elastic-package make -C e2e/_suites/fleet functional-testRelated issues
Follow-ups
We do not need backports but a specific commit using
kibana.config.default.ymlinstead ofkibana.config.8x.yml