João Duarte
João Duarte
if that works, a way to inject it without editing code would be leverage the ruby filter: ```ruby filter { # ... ruby { init => 'Aws.config[:ssl_verify_peer] = false' code...
Thanks for the PR @teancom, I have restarted the tests in travis
you can install a new integration plugin that moves all aws-related plugins to the new sdk. However you need to uninstall all individual plugins before installing [logstash-integration-aws](https://rubygems.org/gems/logstash-integration-aws/versions/7.0.0): ``` /tmp/logstash-8.3.2 ❯...
I'm guessing that you had to convert the key from pkcs1 to pkcs8. We should likely support pkcs1, 8 and 12, prs welcome :)
> We cannot release minor- or patch-level updates of gems that cannot be installed on older Logstashes; this would be a breaking change, and would warrant major version bumps in...
Adding a terminology audit task that will result in breaking changes https://github.com/elastic/logstash/issues/12052
@roaksoax no, this is a follow up to the PR. The PR removes 1 particular cipher we know we don't want, but the list is still outdated. Updating it will...
fixed in #176
Many thanks @guyboertje ! I'll soon do a transfer to Elastic and reach out to some of the owners of gems that depend on this one. To be able to...
Awesome, I logged into the email and ack'ed it. Many thanks again :)