icingabeat/vendor/github.com/elastic/beats/dev-tools
Blerim Sheqa 0fc9123310 Update to libbeat 5.6 2017-12-18 10:56:10 +01:00
..
packer Update to libbeat 5.6 2017-12-18 10:56:10 +01:00
vendor Update to libbeat 5.3.0 2017-04-18 14:08:57 +02:00
.beatconfig Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
README.md Update to libbeat 5.3.0 2017-04-18 14:08:57 +02:00
aggregate_coverage.py Update to libbeat 5.3.0 2017-04-18 14:08:57 +02:00
cherrypick_pr Update to libbeat 5.6 2017-12-18 10:56:10 +01:00
common.bash Update to libbeat 5.6 2017-12-18 10:56:10 +01:00
deploy Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
export_dashboards.py Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
generate_notice.py Update to libbeat 5.3.0 2017-04-18 14:08:57 +02:00
get_version Update to libbeat 5.2.2 2017-03-15 09:54:31 +01:00
glide.yaml Update to libbeat 5.3.0 2017-04-18 14:08:57 +02:00
jenkins_ci.ps1 Update to libbeat 5.6 2017-12-18 10:56:10 +01:00
jenkins_ci.sh Update to libbeat 5.6 2017-12-18 10:56:10 +01:00
jenkins_intake.sh Update to libbeat 5.6 2017-12-18 10:56:10 +01:00
merge_pr Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
package_test.go Update to libbeat 5.3.2 2017-04-28 15:17:44 +02:00
requirements.txt Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
run_with_go_ver Update to libbeat 5.2.2 2017-03-15 09:54:31 +01:00
set_version Update to libbeat 5.2.2 2017-03-15 09:54:31 +01:00

README.md

Available scripts

The following scripts are used by the unified release process:

File Description
get_version Returns the current version
set_version Sets the current version in all places where change is required. Doesn't commit changes.
deploy Builds all artifacts for the officially supported Beats

Other scripts:

File Description
aggregate_coverage.py Used to create coverage reports that contain both unit and system tests data
merge_pr Used to make it easier to open a PR that merges one branch into another.

Import / export the dashboards of a single Beat:

File Description
import_dashboards.sh Bash script to import the Beat dashboards from a local directory in Elasticsearch
import_dashboards.ps1 Powershell script to import the Beat dashboards from a local directory in Elasticsearch
export_dashboards.py Python script to export the Beat dashboards from Elasticsearch to a local directory

Running export_dashboards.py in environment

If you are running the python script for the first time, you need to create the environment by running the following commands in the beats/dev-tools directory:

virtualenv env
. env/bin/activate
pip install -r requirements.txt

This creates the environment that contains all the python packages required to run the export_dashboards.py script. Thus, for the next runs you just need to enable the environment:

. env/bin/activate