This plugin is now interruptable, this plugin require a bit more care to
shutdown it down for a few reasons:
It can be stuck streaming file to disk from a S3 bucket.
It can be stuck reading a large file
For case 1, we cancel the streaming and delete the incomplete temp file
and not update the sincedb.
For case 2, we will cancel reading the file and not update the sincedb,
this will result in duplicates in the logging stream which is fine for now since the S3 plugin
doesn't support saving offset yet. see #54
This PR also add a fix to non deterministic test run in a local
environment by specifying a new sincedb for each run.
This plugin is now interruptable, this plugin require a bit more care to shutdown it down for a few reasons:
For case 1, we cancel the streaming and delete the incomplete temp file and not update the sincedb.
For case 2, we will cancel reading the file and not update the sincedb, this will result in duplicates in the logging stream which is fine for now since the S3 plugin doesn't support saving offset yet. see #54
This PR also add a fix to non deterministic test run in a local environment by specifying a new sincedb for each run.
Fixes: #53 #42