You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+7-4
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,8 @@
1
+
## 10.2.3
2
+
- Fixed 8.x type removal compatibility issue to continue for monitoring endpoint from LogStash's X-Pack[#899](https://github.com/logstash-plugins/logstash-output-elasticsearch/pull/899)
3
+
1
4
## 10.2.2
2
-
- Fixed 8.x type removal compatibility issue [#892](https://github.com/logstash-plugins/logstash-output-elasticsearch/pull/892)
5
+
- Fixed 8.x type removal compatibility issue [#892](https://github.com/logstash-plugins/logstash-output-elasticsearch/pull/892)
3
6
4
7
## 10.2.1
5
8
- Fixed wording and corrected option in documentation [#881](https://github.com/logstash-plugins/logstash-output-elasticsearch/pull/881)[#883](https://github.com/logstash-plugins/logstash-output-elasticsearch/pull/883)
@@ -168,14 +171,14 @@
168
171
169
172
## 6.2.3
170
173
- Fixed a bug introduced in 6.2.2 where passwords needing escapes were not actually sent to ES properly
171
-
encoded.
174
+
encoded.
172
175
173
176
## 6.2.2
174
177
- Fixed a bug that forced users to URL encode the `password` option.
175
178
If you are currently manually escaping your passwords upgrading to this version
176
179
will break authentication. You should unescape your password if you have implemented
177
180
this workaround as it will otherwise be doubly encoded.
178
-
URL escaping is STILL required for passwords inline with URLs in the `hosts` option.
181
+
URL escaping is STILL required for passwords inline with URLs in the `hosts` option.
179
182
180
183
## 6.2.1
181
184
- When an HTTP error is encountered, log the response body instead of the request.
@@ -189,7 +192,7 @@
189
192
190
193
## 6.0.0
191
194
- Proxies requiring auth now always work when a URL is specified
192
-
- It is no longer possible to specify a proxy as a hash due to security reasons
195
+
- It is no longer possible to specify a proxy as a hash due to security reasons
193
196
- Fix URL normalization logic to correctly apply all settings to sniffed hosts
194
197
- Proxies requiring auth now always work when a URL is specified
195
198
- Switch internals to new LogStash::Util::SafeURI type for more defensive approach to logging credentials
Copy file name to clipboardExpand all lines: logstash-output-elasticsearch.gemspec
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
Gem::Specification.newdo |s|
2
2
s.name='logstash-output-elasticsearch'
3
-
s.version='10.2.2'
3
+
s.version='10.2.3'
4
4
s.licenses=['apache-2.0']
5
5
s.summary="Stores logs in Elasticsearch"
6
6
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"
0 commit comments