logstash-input-jms 3.1.0-java → 3.1.1-java

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0c67e7b1c2a2cdef01628e322b3d7e7f2b0d569354c4284b667b30ed9ca874d5
-  data.tar.gz: 10f7a99686215d53cd59145a898c0b931763eca6ff20d5a4cd82ababde5b65ba
+  metadata.gz: 43d374bc1470971209a72c56243b04221ecc0af188a3b5ee8d3c816ca1636770
+  data.tar.gz: 386171f7028e2683595d3b82f59f4a9a8ef640f732931f6c4d5b049efedaecd1
 SHA512:
-  metadata.gz: 9fb991ca333e90e0900d36ddac2c299e46805f911d8a3f357a3794bcbab74638d7e63496bb35bb18f4ea7940a266336ab88082193a8f554b87b552c3ea6df17a
-  data.tar.gz: 0e86a615ad62ddc0a9a59d228debdc62cbb2e31f0994146754fc015e9c6cafa828873b462fcd3eaf970902fa2760ec193f9fa92ee5279fdf3d5bb5f7f1d7844e
+  metadata.gz: e20a3c2b9a67b6fe98b58a892fa722ded77d3a9084ea593bf40879cadad6bf7b688860722e8b019339c982b60b73372cf58af641beaf061b0f1f9916f6f33dd1
+  data.tar.gz: 6f7cd9f1c40b186f25815572f1db10f66c0d62f837c03d5cafdf655a53bc046cfab3a573a71bb06b66622c76f1ee10713f538bb7ebe958d6f9f10b5c39b96b82

data/CHANGELOG.md

@@ -1,3 +1,6 @@
+## 3.1.1
+ - Added documentation for `factory_settings` configuration setting [#36](https://github.com/logstash-plugins/logstash-input-jms/pull/36)
+
 ## 3.1.0
  - Added many improvements to plugin [#35](https://github.com/logstash-plugins/logstash-input-jms/pull/35), including:  
    - Added support for TLS

data/docs/index.asciidoc

@@ -36,7 +36,6 @@ JMS configurations can be done either entirely in the Logstash configuration fil
 
 ==== Sample Configuration using Logstash Configuration Only
 
-
 Configurations can be configured either entirely in Logstash configuration, or via a combination of Logstash configuration
 and yaml file, which can be useful for sharing similar configurations across multiple inputs and outputs.
 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.
 <7> Keystore and Truststore to use when connecting to the JMS provider, if required.
 <8> Parts of the JMS Message to include in the event - headers, properties and the message body can be included or
     excluded from the event.
-
 <9> Message selector: Use this to filter messages to be processed. The whole selector query should be double-quoted,
     string property values should be single quoted, and numeric property vaues should not be quoted.
     See JMS provider documentation for exact syntax.
@@ -351,6 +349,7 @@ This plugin supports the following configuration options plus the <<plugins-{typ
 | <<plugins-{type}s-{plugin}-durable_subscriber_client_id>> |<<string,string>>|No
 | <<plugins-{type}s-{plugin}-durable_subscriber_name>> |<<string,string>>|No
 | <<plugins-{type}s-{plugin}-factory>> |<<string,string>>|No
+| <<plugins-{type}s-{plugin}-factory_settings>> |<<hash,hash>>|No
 | <<plugins-{type}s-{plugin}-include_body>> |<<boolean,boolean>>|No
 | <<plugins-{type}s-{plugin}-include_header>> |<<boolean,boolean>>|No
 | <<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
 
 Full name (including package name) of Java connection factory used to create a connection with your JMS provider.
 
+[id="plugins-{type}s-{plugin}-factory_settings"]
+===== `factory_settings`
+
+  * Value type is <<hash,hash>>
+  * There is no default value for this setting.
+
+Hash of implementation specific configuration values to set on the connection factory of the JMS provider. Each JMS
+ Provider will have its own set of parameters that can be used here. These parameters are mapped to `set` methods on
+ the provided connection factory, and can be supplied in either 'snake' or 'camel' case. For example, a hash including
+ `exclusive_consumer => true` would call `setExclusiveConsumer(true)` on the supplied connection factory.
+ See your JMS provider documentation for implementation specific details.
+
 [id="plugins-{type}s-{plugin}-include_body"]
 ===== `include_body`
 

data/logstash-input-jms.gemspec

@@ -1,7 +1,7 @@
 Gem::Specification.new do |s|
 
   s.name            = 'logstash-input-jms'
-  s.version         = '3.1.0'
+  s.version         = '3.1.1'
   s.licenses        = ['Apache License (2.0)']
   s.summary         = "Reads events from a Jms Broker"
   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

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: logstash-input-jms
 version: !ruby/object:Gem::Version
-  version: 3.1.0
+  version: 3.1.1
 platform: java
 authors:
 - Elasticsearch
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2019-06-17 00:00:00.000000000 Z
+date: 2019-07-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement