logstash-input-jms 3.1.0-java → 3.1.1-java
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/CHANGELOG.md +3 -0
- data/docs/index.asciidoc +13 -2
- data/logstash-input-jms.gemspec +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 43d374bc1470971209a72c56243b04221ecc0af188a3b5ee8d3c816ca1636770
|
|
4
|
+
data.tar.gz: 386171f7028e2683595d3b82f59f4a9a8ef640f732931f6c4d5b049efedaecd1
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: e20a3c2b9a67b6fe98b58a892fa722ded77d3a9084ea593bf40879cadad6bf7b688860722e8b019339c982b60b73372cf58af641beaf061b0f1f9916f6f33dd1
|
|
7
|
+
data.tar.gz: 6f7cd9f1c40b186f25815572f1db10f66c0d62f837c03d5cafdf655a53bc046cfab3a573a71bb06b66622c76f1ee10713f538bb7ebe958d6f9f10b5c39b96b82
|
data/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,6 @@
|
|
|
1
|
+
## 3.1.1
|
|
2
|
+
- Added documentation for `factory_settings` configuration setting [#36](https://github.com/logstash-plugins/logstash-input-jms/pull/36)
|
|
3
|
+
|
|
1
4
|
## 3.1.0
|
|
2
5
|
- Added many improvements to plugin [#35](https://github.com/logstash-plugins/logstash-input-jms/pull/35), including:
|
|
3
6
|
- Added support for TLS
|
data/docs/index.asciidoc
CHANGED
|
@@ -36,7 +36,6 @@ JMS configurations can be done either entirely in the Logstash configuration fil
|
|
|
36
36
|
|
|
37
37
|
==== Sample Configuration using Logstash Configuration Only
|
|
38
38
|
|
|
39
|
-
|
|
40
39
|
Configurations can be configured either entirely in Logstash configuration, or via a combination of Logstash configuration
|
|
41
40
|
and yaml file, which can be useful for sharing similar configurations across multiple inputs and outputs.
|
|
42
41
|
The JMS plugin can also be configured using JNDI if desired.
|
|
@@ -86,7 +85,6 @@ The JMS plugin can also be configured using JNDI if desired.
|
|
|
86
85
|
<7> Keystore and Truststore to use when connecting to the JMS provider, if required.
|
|
87
86
|
<8> Parts of the JMS Message to include in the event - headers, properties and the message body can be included or
|
|
88
87
|
excluded from the event.
|
|
89
|
-
|
|
90
88
|
<9> Message selector: Use this to filter messages to be processed. The whole selector query should be double-quoted,
|
|
91
89
|
string property values should be single quoted, and numeric property vaues should not be quoted.
|
|
92
90
|
See JMS provider documentation for exact syntax.
|
|
@@ -351,6 +349,7 @@ This plugin supports the following configuration options plus the <<plugins-{typ
|
|
|
351
349
|
| <<plugins-{type}s-{plugin}-durable_subscriber_client_id>> |<<string,string>>|No
|
|
352
350
|
| <<plugins-{type}s-{plugin}-durable_subscriber_name>> |<<string,string>>|No
|
|
353
351
|
| <<plugins-{type}s-{plugin}-factory>> |<<string,string>>|No
|
|
352
|
+
| <<plugins-{type}s-{plugin}-factory_settings>> |<<hash,hash>>|No
|
|
354
353
|
| <<plugins-{type}s-{plugin}-include_body>> |<<boolean,boolean>>|No
|
|
355
354
|
| <<plugins-{type}s-{plugin}-include_header>> |<<boolean,boolean>>|No
|
|
356
355
|
| <<plugins-{type}s-{plugin}-include_properties>> |<<boolean,boolean>>|No
|
|
@@ -444,6 +443,18 @@ is set to `true`. Please consult your JMS Provider documentation for constraints
|
|
|
444
443
|
|
|
445
444
|
Full name (including package name) of Java connection factory used to create a connection with your JMS provider.
|
|
446
445
|
|
|
446
|
+
[id="plugins-{type}s-{plugin}-factory_settings"]
|
|
447
|
+
===== `factory_settings`
|
|
448
|
+
|
|
449
|
+
* Value type is <<hash,hash>>
|
|
450
|
+
* There is no default value for this setting.
|
|
451
|
+
|
|
452
|
+
Hash of implementation specific configuration values to set on the connection factory of the JMS provider. Each JMS
|
|
453
|
+
Provider will have its own set of parameters that can be used here. These parameters are mapped to `set` methods on
|
|
454
|
+
the provided connection factory, and can be supplied in either 'snake' or 'camel' case. For example, a hash including
|
|
455
|
+
`exclusive_consumer => true` would call `setExclusiveConsumer(true)` on the supplied connection factory.
|
|
456
|
+
See your JMS provider documentation for implementation specific details.
|
|
457
|
+
|
|
447
458
|
[id="plugins-{type}s-{plugin}-include_body"]
|
|
448
459
|
===== `include_body`
|
|
449
460
|
|
data/logstash-input-jms.gemspec
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
Gem::Specification.new do |s|
|
|
2
2
|
|
|
3
3
|
s.name = 'logstash-input-jms'
|
|
4
|
-
s.version = '3.1.
|
|
4
|
+
s.version = '3.1.1'
|
|
5
5
|
s.licenses = ['Apache License (2.0)']
|
|
6
6
|
s.summary = "Reads events from a Jms Broker"
|
|
7
7
|
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-jms
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 3.1.
|
|
4
|
+
version: 3.1.1
|
|
5
5
|
platform: java
|
|
6
6
|
authors:
|
|
7
7
|
- Elasticsearch
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2019-
|
|
11
|
+
date: 2019-07-08 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
requirement: !ruby/object:Gem::Requirement
|