Releases: logstash-plugins/logstash-output-google_cloud_storage
Releases · logstash-plugins/logstash-output-google_cloud_storage
Move to the Java Google Cloud client library for increased performance and stability
Notes
- Move to the Java Google Cloud client library for increased performance and stability.
- Breaking If you use the old PKCS12 authentication keys, you will need to upgrade to
the new JSON keys. Application Default Credentials will continue to work.
Configuration Changes
New Options
json_key_file
- The JSON IAM service account credentials to use with the plugin.
Deprecations
key_password
- No longer used withjson_key_file
service_account
- No longer used withjson_key_file
Obsoletions
key_path
- Usejson_key_file
or Application Default Credentials (ADC) instead.
See the documentation
for help about moving to JSON key files.
Added the ability to set `gzip` as `Content-Encoding`
Added the ability to set gzip
as Content-Encoding
.
This saves storage size but still allows uncompressed downloads.
- Fixes #13 - Use
gzip
forContent-Encoding
instead ofContent-Type
Added Locking and Invariant
Job Pools
v3.1.0: Log UUID inclusion, fixes #23 (#26)
Added the ability to include/exclude the hostname and a UUID in the filename. This will solve possible race conditions when running multiple instances of the plugin dumping into the same bucket, as well as allow a glob with a single pattern to match files (useful for uploading to BigQuery). On a technical side the file name generation code has been broken out and is now thread-safe which takes us part of the way toward fixing #2.