Allow passing instance of AwsCredentialsProvider to configuration

[joshfriend]

This enables being more explicit about the provider chain to use in cases where the lookupDefaultAwsCredentials is not viable, or where you have a custom subclass of AwsCredentialsProvider you need to use.

[vlsi]

I am afraid passing non-trivial objects to the build cache configuration would break Gradle configuration cache (see cd5dc7f#diff-c071312d40ceebf75a3042495b63d3ef210a1dcfaf0d45d48e5053363105942aL48 ).

Could you please add a test (e.g. to

gradle-s3-build-cache/src/test/kotlin/com/github/burrunan/s3cache/RemoteCacheTest.kt

Lines 127 to 135 in 4d26ab7

	remote(com.github.burrunan.s3cache.AwsS3BuildCache) {
	region = 'eu-west-1'
	bucket = '$BUCKET_NAME'
	prefix = 'build-cache/'
	endpoint = 'localhost:${mockApp.port}'
	// See https://github.com/adobe/S3Mock/issues/880
	forcePathStyle = true
	push = true
	}

) to ensure the configuration you provide supports configuration cache?

[joshfriend]

Added a very basic example to the test fixture. I think maybe just making the S3Client creation lazy in that previous commit was all that is really needed to be configuration cache compatible.

I tested some of my own builds with this and gradle reported no issues with it.

[vlsi]

Great, thank you

[vlsi]

Will release it shortly

[joshfriend]

We've been using this with a custom AwsCredentialsProvider for a while now and it has been working well. I would like to move off of using our internally hosted fork though, can you please make a new release available?

[vlsi]

Wow. I thought I released this. Let me check it again.

[vlsi]

I've published 1.7 to Central and GPP. Sorry for the delay, and thanks for the reminder.