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
If set, the plugin will store the list of processed files locally. This allows you to create a service account for the plugin that does not have write permissions. However, the data will not be shared across multiple running instances of Logstash.
This implies that it should be possible to omit processed_db_path and not have Logstash write to the local filesystem all the files it has processed, and instead rely solely on the metadata key and/or deleting processed files.
However processed_db_path is always assumed and the logic surrounding it cannot be avoided from what I can see
Description:
The docs for input plugin specify:
This implies that it should be possible to omit
processed_db_path
and not have Logstash write to the local filesystem all the files it has processed, and instead rely solely on the metadata key and/or deleting processed files.However
processed_db_path
is always assumed and the logic surrounding it cannot be avoided from what I can seelogstash-input-google_cloud_storage/lib/logstash/inputs/google_cloud_storage.rb
Lines 44 to 47 in 079b5f1
URL:
Example: https://www.elastic.co/guide/en/logstash/current/introduction.html
Anything else?
Not 100% clear if this is a documentation issue or the feature/support for not specifying the property was not correctly implemented
The text was updated successfully, but these errors were encountered: