logstash-input-elastic_serverless_forwarder 0.1.1-java → 0.1.2-java

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 0e68d73969ef8dec415c74ce755da13dfa6bad59c99c239e439b5edafd856ea8
4
- data.tar.gz: e3d07f9b40953bf1e44b0f26a63beef226aac28bf03b05286e0e90b67ebe60ce
3
+ metadata.gz: 14190aec17bc2282d956db77e43a6118fbbe8ed156e53ca295f9064b202706b1
4
+ data.tar.gz: 2bcb76de61764a863882b3f40d9af35d2ff9867b0d8a00d31346e81a677c00f7
5
5
  SHA512:
6
- metadata.gz: 8ff5d1b69d172f1293db93a316515779dd68875425b514517ae94edb9f807b5705a40cfeff2b4d613e62b497401a074695ca7abbe65ded013906aad1bbbca459
7
- data.tar.gz: abf8b62a5135fc746a38709d43252e9447faae8c10d8c8e434bf70034fe9bdc13e76c346046cd58e6a37dc9728a0126c50dbae07c1ec27b245b4b352367ab5e7
6
+ metadata.gz: db6ad54b41a91e677c45a4b73534499b892b34788abb1dcbba699d30df0fdf389b193f459727bac9af6c3010c82d2b4c30d6afb1eb663da5e61117a4f826feea
7
+ data.tar.gz: 65f652cf3a00c6a17006c15567b26d5ded49674c31c75ccfa03e6663c9d3494cbcc009f941c3227a36d5af8897853b4ece9a3fc598ad444877c7558594cd0797
data/CHANGELOG.md CHANGED
@@ -1,3 +1,6 @@
1
+ ## 0.1.2
2
+ - [DOC] Adds "Technical Preview" call-out to documentation [#4](https://github.com/logstash-plugins/logstash-input-elastic_serverless_forwarder/pull/4)
3
+
1
4
  ## 0.1.1
2
5
  - Fixes an issue that prevents this prototype from being instantiated in an actual Logstash pipeline [#3](https://github.com/logstash-plugins/logstash-input-elastic_serverless_forwarder/pull/3)
3
6
 
data/docs/index.asciidoc CHANGED
@@ -26,7 +26,7 @@ include::{include_path}/plugin_header.asciidoc[]
26
26
  Using this input you can receive events from {esf-name} over http(s) connections to the configured <<plugins-{type}s-{plugin}-port>>.
27
27
 
28
28
  [id="plugins-{type}s-{plugin}-ext-field"]
29
- ====== Minimum Configuration
29
+ ===== Minimum Configuration
30
30
  [cols="3a,2a"]
31
31
  |=======================================================================================================================
32
32
  |SSL Enabled |SSL Disabled
@@ -58,13 +58,26 @@ input {
58
58
 
59
59
  |=======================================================================================================================
60
60
 
61
+ .Technical Preview
62
+ ****
63
+ This {esf-name} input plugin is part of a _Technical Preview_, which means that both configuration options and implementation details are subject to change in minor releases without being preceded by deprecation warnings.
64
+
65
+ Before upgrading this plugin or Logstash itself, please pay special attention to this plugin's https://github.com/logstash-plugins/logstash-input-elastic_serverless_forwarder/blob/main/CHANGELOG.md[CHANGELOG.md] to avoid being caught by surprise.
66
+ ****
67
+
68
+
61
69
  [id="plugins-{type}s-{plugin}-enrichment"]
62
70
  ==== Enrichment
63
71
 
64
72
  This input provides _minimal enrichment_ on events, and avoids including information about itself, the client from which it received the data, or about the original event as-decoded from the request.
65
- If the decoded event has a valid ISO8601-encoded `@timestamp`, it will be used. Otherwise this required field will be populated with the current time.
66
73
 
67
74
  NOTE: Senders are advised to use care with respect to fields that are {logstash-ref}/processing.html#reserved-fields[reserved in Logstash].
75
+ ESF sends the Logstash-required `@timestamp` field by default, but if this value is missing it will be populated with the current time.
76
+
77
+
78
+ ////
79
+ // BEGIN: Elastic-internal implementation details
80
+ //
68
81
 
69
82
  [id="plugins-{type}s-{plugin}-blocking"]
70
83
  ==== Blocking Behavior
@@ -76,6 +89,10 @@ A client that receives an HTTP request timeout is expected to retry the entire r
76
89
  When this plugin is blocked, it will reject _new_ requests with HTTP `429 Too Many Requests`.
77
90
  Clients that receive `429`-s are expected to wait a moment before retrying the request — exponential back-off is encouraged to ease flood recovery.
78
91
 
92
+ //
93
+ // END: Elastic-internal implementation details
94
+ ////
95
+
79
96
  [id="plugins-{type}s-{plugin}-security"]
80
97
  ==== Security
81
98
 
@@ -87,7 +104,7 @@ Additionally, you may wish to authenticate clients using SSL client authenticati
87
104
 
88
105
  ===== SSL Identity
89
106
 
90
- In order to establish SSL with a client, this input plugin will need to present an SSL certificate that the client trusts and have access to the associated key.
107
+ In order to establish SSL with a client, this input plugin will need to present an SSL certificate that the client trusts, and have access to the associated key.
91
108
  These are configurable with <<plugins-{type}s-{plugin}-ssl_certificate>>, <<plugins-{type}s-{plugin}-ssl_key>>, and optionally <<plugins-{type}s-{plugin}-ssl_key_passphrase>>.
92
109
 
93
110
  ===== SSL Client Authentication
@@ -98,6 +115,8 @@ It can be configured to either request or require client certificates using <<pl
98
115
  which often also requires configuring it with a list of <<plugins-{type}s-{plugin}-ssl_certificate_authorities>> to trust.
99
116
  When validating a certificate that is presented, <<plugins-{type}s-{plugin}-ssl_verification_mode>> controls how certificates are verified.
100
117
 
118
+ NOTE: ESF does not currently support _presenting_ client certificates, so requesting or requiring clients to present identity is only useful when combined with an SSL-terminating proxy.
119
+
101
120
  ===== SSL Advanced Configuration
102
121
 
103
122
  This plugin exposes several advanced SSL configurations:
@@ -233,7 +252,7 @@ For example, the ChaCha20 family of ciphers is not supported in older versions.
233
252
  * Default value is `"none"`
234
253
 
235
254
  By default the server doesn't do any client authentication.
236
- This means that connections from clients are private by default, but that this input will allow SSL connections from _any_ client.
255
+ This means that connections from clients are _private_ when SSL is enabled, but that this input will allow SSL connections from _any_ client.
237
256
  If you wish to configure this plugin to reject connections from untrusted hosts, you will need to configure this plugin to authenticate clients, and may also need to configure it with a list of `ssl_certificate_authorities`.
238
257
 
239
258
  [id="plugins-{type}s-{plugin}-ssl_handshake_timeout"]
@@ -2,7 +2,7 @@
2
2
 
3
3
  Gem::Specification.new do |s|
4
4
  s.name = 'logstash-input-elastic_serverless_forwarder'
5
- s.version = '0.1.1'
5
+ s.version = '0.1.2'
6
6
  s.licenses = ['Apache License (2.0)']
7
7
  s.summary = "Receives events from Elastic Serverless Forwarder over HTTP or HTTPS"
8
8
  s.description = "This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. This gem is not a stand-alone program"
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: logstash-input-elastic_serverless_forwarder
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.1
4
+ version: 0.1.2
5
5
  platform: java
6
6
  authors:
7
7
  - Elastic
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2023-01-05 00:00:00.000000000 Z
11
+ date: 2023-02-10 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  requirement: !ruby/object:Gem::Requirement