Support default object expiration

[bradrydzewski]

This could be useful when combined with our existing flush logic
https://aws.amazon.com/about-aws/whats-new/2011/12/27/amazon-s3-announces-object-expiration/

For example imagine that we have a small node project with a below average amount of dependencies that results in a 1GB cache file 😈 . If the project is inactivate (or is deleted), builds are not running, and files might not get flushed. Expiration could be a useful fallback here.

[tboerger]

Do you have some proper yaml schema for that in mind? With the latest Minio sdk this can be integrated.

[donny-dont]

Do you think the default branch should have a different expiration time?

[tboerger]

I guess that's up to the drone user :)

[ewang]

Another way to support this for S3 without changing the plugin is to leverage lifecycle rules at the bucket level.