Remove extraneous imports from security endpoint

elastic · Feb 18, 2021 · ce484ea · ce484ea
1 parent 39ac15d
commit ce484ea
Showing 1 changed file with 0 additions and 7 deletions.
diff --git a/x-pack/test/fleet_functional/config.ts b/x-pack/test/fleet_functional/config.ts
@@ -9,10 +9,6 @@ import { resolve } from 'path';
 import { FtrConfigProviderContext } from '@kbn/test/types/ftr';
 import { pageObjects } from './page_objects';
 import { services } from './services';
-import {
-  getRegistryUrlAsArray,
-  createEndpointDockerConfig,
-} from '../security_solution_endpoint_api_int/registry';
 
 export default async function ({ readConfigFile }: FtrConfigProviderContext) {
   const xpackFunctionalConfig = await readConfigFile(require.resolve('../functional/config.js'));
@@ -21,7 +17,6 @@ export default async function ({ readConfigFile }: FtrConfigProviderContext) {
     ...xpackFunctionalConfig.getAll(),
     pageObjects,
     testFiles: [resolve(__dirname, './apps/fleet')],
-    dockerServers: createEndpointDockerConfig(),
     junit: {
       reportName: 'X-Pack Fleet Functional Tests',
     },
@@ -37,8 +32,6 @@ export default async function ({ readConfigFile }: FtrConfigProviderContext) {
       serverArgs: [
         ...xpackFunctionalConfig.get('kbnTestServer.serverArgs'),
         '--xpack.fleet.enabled=true',
-        // if you return an empty string here the kibana server will not start properly but an empty array works
-        ...getRegistryUrlAsArray(),
       ],
     },
     layout: {