Update logstash 7.7.1 -> 7.8.0
Release notes: https://www.elastic.co/guide/en/logstash/7.8/logstash-7-8-0.html
This commit is contained in:
parent
88c2676f65
commit
4b6ae520e7
@ -1,9 +1,9 @@
|
||||
# $OpenBSD: Makefile,v 1.36 2020/06/16 12:03:26 pvk Exp $
|
||||
# $OpenBSD: Makefile,v 1.37 2020/07/01 12:00:51 pvk Exp $
|
||||
|
||||
ONLY_FOR_ARCHS = amd64
|
||||
COMMENT = tool for managing events and logs
|
||||
|
||||
V = 7.7.1
|
||||
V = 7.8.0
|
||||
DISTNAME = logstash-oss-$V
|
||||
PKGNAME = logstash-$V
|
||||
EPOCH = 0
|
||||
|
@ -1,4 +1,4 @@
|
||||
SHA256 (logstash-oss-7.7.1.tar.gz) = xWZAOpqkvcsUFMEZGY0jNumUe2ZA3HYeSv262mRqs3Y=
|
||||
SHA256 (logstash-oss-7.8.0.tar.gz) = SLWdKyDxsL0hy/OqcZ/1FUGhYWa8oNgpi7di4joSnUI=
|
||||
SHA256 (netty-tcnative-boringssl-static-2.0.12.Final.jar) = mRxDzTZmeAmxpLn6G8apMySkRqOMb7cXFpiS09RZCwk=
|
||||
SIZE (logstash-oss-7.7.1.tar.gz) = 166269972
|
||||
SIZE (logstash-oss-7.8.0.tar.gz) = 166982219
|
||||
SIZE (netty-tcnative-boringssl-static-2.0.12.Final.jar) = 1156667
|
||||
|
@ -1,4 +1,4 @@
|
||||
$OpenBSD: patch-config_logstash_yml,v 1.7 2020/05/14 21:42:48 pvk Exp $
|
||||
$OpenBSD: patch-config_logstash_yml,v 1.8 2020/07/01 12:00:51 pvk Exp $
|
||||
|
||||
Index: config/logstash.yml
|
||||
--- config/logstash.yml.orig
|
||||
@ -12,7 +12,7 @@ Index: config/logstash.yml
|
||||
#
|
||||
# ------------ Pipeline Settings --------------
|
||||
#
|
||||
@@ -217,7 +217,7 @@ pipeline.ordered: auto
|
||||
@@ -238,7 +238,7 @@ pipeline.ordered: auto
|
||||
# * trace
|
||||
#
|
||||
# log.level: info
|
||||
@ -21,7 +21,7 @@ Index: config/logstash.yml
|
||||
#
|
||||
# ------------ Other Settings --------------
|
||||
#
|
||||
@@ -227,43 +227,3 @@ pipeline.ordered: auto
|
||||
@@ -248,43 +248,3 @@ pipeline.ordered: auto
|
||||
# Flag to output log lines of each pipeline in its separate log file. Each log filename contains the pipeline.name
|
||||
# Default is false
|
||||
# pipeline.separate_logs: false
|
||||
|
File diff suppressed because it is too large
Load Diff
Loading…
Reference in New Issue
Block a user