logstash-output-vespa_feed 0.4.0 → 0.5.0

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 CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: f560b57ecd2a25e2a50a6640a90c9803077474b090fe1d539c24cf2cdabc362e
4
- data.tar.gz: 25ca7fa19e63fc3863f7c9576dcdaa4b1c7a74dbecd1758c5f2e455414e396c6
3
+ metadata.gz: 186273bc178047bdc0a838874803aca962a710909b924a517a384623342aa4ac
4
+ data.tar.gz: 542044e824ed65a1f2f3bdd5230c960cd2d96a4a2c073f27191db3c5d98ab5ef
5
5
  SHA512:
6
- metadata.gz: ba80b8fcab865ea83e71a1d9e75c782335991001be58c08cc51756ce1c4488c6810501f35f5a504ae7fdf5a740512bbf74978b61ce31f555a543339ab2ab4292
7
- data.tar.gz: 1aacfe2d3ed631bd471669d4c3fe175bec2eb676ad9a90931b55115c8b9d795fe1a7bad0edf90dbefdff2aa0fca04495535ba86462a8a49409b6a6dfe3e2eb4a
6
+ metadata.gz: df61a29d77945ed8451662f3694dccba2494271c2592ab70252eddb39c5214450092868a68ea7cb8b497a8b899cd5b801ce486799a5b8b38501878dff5a4b45b
7
+ data.tar.gz: 9d8fdd12570f6668075b6347a124f3aa1398b0e75f782784ea0607135840f8ed6996958d8583b237c420e03ead6d27f5ba9d2c24641c1a870aba0cbd7ff6ce6f
data/README.md CHANGED
@@ -15,7 +15,7 @@ If you're developing the plugin, you'll want to do something like:
15
15
  # build the gem
16
16
  ./gradlew gem
17
17
  # install it as a Logstash plugin
18
- /opt/logstash/bin/logstash-plugin install /path/to/logstash-output-vespa/logstash-output-vespa_feed-0.3.0.gem
18
+ /opt/logstash/bin/logstash-plugin install /path/to/logstash-output-vespa/logstash-output-vespa_feed-0.4.0.gem
19
19
  # profit
20
20
  /opt/logstash/bin/logstash
21
21
  ```
@@ -74,8 +74,16 @@ output {
74
74
 
75
75
  vespa_feed { # including defaults here
76
76
 
77
- # Vespa endpoint, namespace, doc type (from the schema)
77
+ # Vespa endpoint
78
78
  vespa_url => "http://localhost:8080"
79
+
80
+ # for HTTPS URLS (e.g. Vespa Cloud), you may want to provide a certificate and key for mTLS authentication
81
+ client_cert => "/home/radu/vespa_apps/myapp/security/clients.pem"
82
+ # make sure the key isn't password-protected
83
+ # if it is, you can create a new key without a password like this:
84
+ # openssl rsa -in myapp_key_with_pass.pem -out myapp_key.pem
85
+ client_key => "/home/radu/vespa_apps/myapp_key.pem"
86
+
79
87
  # namespace could be static or in the %{field} format, picking from a field in the document
80
88
  namespace => "no_default_provide_yours"
81
89
  # similarly, doc type could be static or in the %{field} format
data/VERSION CHANGED
@@ -1 +1 @@
1
- 0.4.0
1
+ 0.5.0
data/docs/index.asciidoc CHANGED
@@ -35,6 +35,8 @@ Writes documents to Vespa.
35
35
  |=======================================================================
36
36
  |Setting |Input type|Required
37
37
  | <<plugins-{type}s-{plugin}-vespa_url>> |<<string,string>>|No
38
+ | <<plugins-{type}s-{plugin}-client_cert>> |<<string,string>>|No
39
+ | <<plugins-{type}s-{plugin}-client_key>> |<<string,string>>|No
38
40
  | <<plugins-{type}s-{plugin}-namespace>> |<<string,string>>|Yes
39
41
  | <<plugins-{type}s-{plugin}-document_type>> |<<string,string>>|Yes
40
42
  | <<plugins-{type}s-{plugin}-id_field>> |<<string,string>>|No
@@ -51,7 +53,27 @@ Writes documents to Vespa.
51
53
  * Value type is <<string,string>>
52
54
  * Default value is `http://localhost:8080`
53
55
 
54
- URL to the Vespa instance
56
+ URL to the Vespa instance.
57
+
58
+ If you're using Vespa Cloud, it will be listed as an MTLS endpoint under your application. In this case, make sure to set `client_cert` and `client_key` as well.
59
+
60
+ [id="plugins-{type}s-{plugin}-client_cert"]
61
+ ===== `client_cert`
62
+
63
+ * Value type is <<string,string>>
64
+ * Default value is `nil`
65
+
66
+ Certificate to use for https://blog.vespa.ai/securing-vespa-with-mutually-authenticated-tls/[mTLS authentication]. It's the preferred method to https://cloud.vespa.ai/en/security/guide.html[authenticate with Vespa Cloud], too.
67
+
68
+ Make sure to set the `client_key` as well. The certificate should be in PEM format. Also, the `vespa_url` should be an HTTPS URL.
69
+
70
+ [id="plugins-{type}s-{plugin}-client_key"]
71
+ ===== `client_key`
72
+
73
+ * Value type is <<string,string>>
74
+ * Default value is `nil`
75
+
76
+ Corresponding private key for the `client_cert` certificate. It must not be password-protected, otherwise Logstash will fail to start complaining `Could not find private key in PEM file`.
55
77
 
56
78
  [id="plugins-{type}s-{plugin}-namespace"]
57
79
  ===== `namespace`
@@ -2,4 +2,4 @@
2
2
  # encoding: utf-8
3
3
 
4
4
  require 'jar_dependencies'
5
- require_jar('org.logstashplugins', 'logstash-output-vespa_feed', '0.4.0')
5
+ require_jar('org.logstashplugins', 'logstash-output-vespa_feed', '0.5.0')
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: logstash-output-vespa_feed
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.4.0
4
+ version: 0.5.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Radu Gheorghe
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2024-08-26 00:00:00.000000000 Z
11
+ date: 2024-08-27 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  requirement: !ruby/object:Gem::Requirement
@@ -77,7 +77,7 @@ files:
77
77
  - lib/logstash-output-vespa_feed_jars.rb
78
78
  - lib/logstash/outputs/vespa_feed.rb
79
79
  - logstash-output-vespa_feed.gemspec
80
- - vendor/jar-dependencies/org/logstashplugins/logstash-output-vespa_feed/0.4.0/logstash-output-vespa_feed-0.4.0.jar
80
+ - vendor/jar-dependencies/org/logstashplugins/logstash-output-vespa_feed/0.5.0/logstash-output-vespa_feed-0.5.0.jar
81
81
  homepage: https://vespa.ai
82
82
  licenses:
83
83
  - Apache-2.0