Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Set Certificate Authority in Serverless FTR base config based on MKI (e…
…lastic#165914) ## Summary Follow-up to elastic#165846 Moves the check for cloud/MKI to the base serverless FTR config. We found three use cases where the Kibana server configuration was providing a CA override: 1. In the [serverless supertest](https://github.com/elastic/kibana/blob/49ff1f152e43bc19fbdeb426fd28be372e50b3e4/x-pack/test_serverless/shared/services/supertest.ts#L15) 2. In the [APM API supertest](https://github.com/elastic/kibana/blob/49ff1f152e43bc19fbdeb426fd28be372e50b3e4/x-pack/test_serverless/api_integration/test_suites/observability/apm_api_integration/common/apm_api_supertest.ts#L107C2-L107C2) 3. In the FTR KIbana server's [Kibana client instantiation](https://github.com/elastic/kibana/blob/49ff1f152e43bc19fbdeb426fd28be372e50b3e4/packages/kbn-ftr-common-functional-services/services/kibana_server/kibana_server.ts#L24C1-L24C1) Locally, CA certs should be overridden to our self-singed certs, while on MKI we should default to the Mozilla well-known CAs. Moving the check to the test config (if it proves successful) handles all three cases without the need for adding environment variable checks in multiple places. cc @kc13greiner --------- Co-authored-by: kibanamachine <[email protected]>
- Loading branch information