kibana/scripts/enabled_ftr_configs.js
Dzmitry Lemechko 88464e5b6d
[FTR] split configs by target into multiple manifest files (#187440)
## Summary

Part of #186515

Split FTR configs manifest into multiple files based on distro
(serverless/stateful) and area of testing (platform/solutions)
Update the CI scripts to support the change, but without logic
modification

More context:

With this change we will have a clear split of FTR test configs owned by
Platform and Solutions. It is a starting point to make configs
discoverable, our test pipelines be flexible and run tests based on
distro/solution.
2024-07-19 15:00:53 +02:00

33 lines
1.1 KiB
JavaScript

/*
* Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
* or more contributor license agreements. Licensed under the Elastic License
* 2.0 and the Server Side Public License, v 1; you may not use this file except
* in compliance with, at your election, the Elastic License 2.0 or the Server
* Side Public License, v 1.
*/
require('../src/setup_node_env');
var yaml = require('js-yaml');
var fs = require('fs');
var path = require('path');
var manifestsJsonPath = path.resolve(__dirname, '../.buildkite/ftr_configs_manifests.json');
console.log(manifestsJsonPath);
var manifestsSource = JSON.parse(fs.readFileSync(manifestsJsonPath, 'utf8'));
var allManifestPaths = Object.values(manifestsSource).flat();
try {
for (var manifestRelPath of allManifestPaths) {
var manifest = yaml.load(fs.readFileSync(manifestRelPath, 'utf8'));
if (manifest.enabled) {
manifest.enabled.forEach(function (x) {
console.log(x);
});
} else {
console.log(`${manifestRelPath} has no enabled FTR configs`);
}
}
} catch (e) {
console.log(e);
}