Closed mamccorm closed 5 months ago
There wasn't really any substantive changes, weren't there? Are you looking for a specific fix that was made?
On this note we could use a CHANGELOG like https://github.com/opensearch-project/opensearch-py/blob/main/CHANGELOG.md, maybe you'd be interested in contributing one so we can see easily what is ready to be released?
Hi, can you build a new docker image (https://hub.docker.com/r/opensearchproject/logstash-oss-with-opensearch-output-plugin) based on the latest LOGSTASH_VERSION (https://www.docker.elastic.co/r/logstash/logstash-oss). Current version is LOGSTASH_VERSION=${LOGSTASH_VERSION:-8.3.2}. And lot of current inputs plugins documentation is ahead. IE for tcp input plugin lot of changes since logstash 8.3.2 wich run tcp input plugin 6.3.0. You can't rely on the current documentation https://www.elastic.co/guide/en/logstash/current/plugins-inputs-tcp.html).
Hey @dblock, there are currenrly 237 CVEs in the most recent image, which was last pushed 10 months ago:
A lot of these look like they'd be remediated by rebuilding the image. Given there has been some activity in the repo as well as a long time since the last release / build cut, it'd be great to cut for that reason, or periodically re-trigger a re-build of the image
There was a discussion in this in https://github.com/opensearch-project/logstash-output-opensearch/issues/230, which says we're not planning to make any new docker releases (cc: @dlvenable). But we should talk about it again. Maybe someone can help add automation for it in opensearch-build?
Closing in favor of https://github.com/opensearch-project/logstash-output-opensearch/issues/230.
Hi there,
The last release tag was cut back in Aug 2023. Since then theres been quite a few commits. Any plans to cut a new release tag to pickup these changes?