# Conflicts:
#	logstash/pipeline/logstash.conf

add production data, modify es index generate rule

See merge request !4

# Conflicts:
#   logstash/pipeline/logstash.conf

modify install script

See merge request !3

Release 1.0.1

See merge request !2

# Conflicts:
#   logstash/pipeline/logstash.conf

# Conflicts:
#	start.sh

add v2

See merge request !1

Co-authored-by: antoineco <antoineco@users.noreply.github.com>

Co-authored-by: antoineco <antoineco@users.noreply.github.com>

Fixes #578

Co-authored-by: antoineco <antoineco@users.noreply.github.com>

ci: Update Enterprise Search test for v3 index

App Search API keys are now encrypted in Elasticsearch, so we simply
ensure they exist and don't try to read their value.

Co-authored-by: antoineco <antoineco@users.noreply.github.com>

All secondary branches are regularly rebased onto master, not only the
tls branch.

Co-authored-by: Antoine Cotten <hello@acotten.com>

Co-authored-by: antoineco <antoineco@users.noreply.github.com>

Since v7.10, Logstash prints the following warning message when this
setting is not defined:

[deprecation.logstash.outputs.elasticsearch] Relying on default value of
`pipeline.ecs_compatibility`, which may change in a future major release
of Logstash. To avoid unexpected changes when upgrading Logstash, please
explicitly declare your desired ECS Compatibility mode.

Ref: https://www.elastic.co/guide/en/logstash/7.10/plugins-outputs-elasticsearch.html#plugins-outputs-elasticsearch-ecs_compatibility

Co-authored-by: antoineco <antoineco@users.noreply.github.com>

Co-authored-by: antoineco <antoineco@users.noreply.github.com>