- Fix an issue that prevented timely shutdown when subscribed to an inactive queue #65
- Refactoring: used logstash-mixin-aws to leverage shared code to manage
additional_settings
#64
- Feature: Add
additional_settings
option to fine-grain configuration of AWS client #61
- Feature: Add
queue_owner_aws_account_id
parameter for cross-account queues #60
- Fix: retry networking errors (with backoff) #57
- Added support for multiple events inside same message from SQS #48
- Docs: Set the default_codec doc attribute.
- Add documentation for endpoint, role_arn and role_session_name #46
- Fix sample IAM policy to match to match the documentation #32
- Update gemspec summary
- Fix some documentation issues
- Monkey-patch the AWS-SDK to prevent "uninitialized constant" errors.
- Relax constraint on logstash-core-plugin-api to >= 1.60 <= 2.99
- Republish all the gems under jruby.
- Update the plugin to the version 2.0 of the plugin api, this change is required for Logstash 5.0 compatibility. See elastic/logstash#5141
- Depend on logstash-core-plugin-api instead of logstash-core, removing the need to mass update plugins on major releases of logstash
- New dependency requirements for logstash-core for the 5.0 release
- Fixes #22, wrong key use on the stats object
- Plugins were updated to follow the new shutdown semantic, this mainly allows Logstash to instruct input plugins to terminate gracefully, instead of using Thread.raise on the plugins' threads. Ref: elastic/logstash#3895
- Dependency on logstash-core update to 2.0
- AWS ruby SDK v2 upgrade
- Replaces aws-sdk dependencies with mixin-aws
- Removes unnecessary de-allocation
- Move the code into smaller methods to allow easier mocking and testing
- Add the option to configure polling frequency
- Adding a monkey patch to make sure
LogStash::ShutdownSignal
doesn't get catch by AWS RetryError.