Revert implementation of POST /api/beats/configuration_blocks API (#…

…19340)

This API allowed the user to operate at a level of abstraction that is unnecessarily and dangerously too low. A better API would be at one level higher, where users can create, update, and delete tags (where a tag can contain multiple configuration blocks).

x-pack/plugins/beats/server/routes/api/index.js

@@ -9,13 +9,11 @@ import { registerEnrollBeatRoute } from './register_enroll_beat_route';
 import { registerListBeatsRoute } from './register_list_beats_route';
 import { registerVerifyBeatsRoute } from './register_verify_beats_route';
 import { registerUpdateBeatRoute } from './register_update_beat_route';
-import { registerCreateConfigurationBlockRoute } from './register_create_configuration_block_route';
 
 export function registerApiRoutes(server) {
   registerCreateEnrollmentTokensRoute(server);
   registerEnrollBeatRoute(server);
   registerListBeatsRoute(server);
   registerVerifyBeatsRoute(server);
   registerUpdateBeatRoute(server);
-  registerCreateConfigurationBlockRoute(server);
 }

x-pack/test/api_integration/apis/beats/index.js

@@ -22,6 +22,5 @@ export default function ({ getService, loadTestFile }) {
     loadTestFile(require.resolve('./list_beats'));
     loadTestFile(require.resolve('./verify_beats'));
     loadTestFile(require.resolve('./update_beat'));
-    loadTestFile(require.resolve('./create_configuration_block'));
   });
 }