s3fs-fuse/test/s3proxy.conf

s3proxy.secure-endpoint=https://127.0.0.1:8080
s3proxy.authorization=aws-v2-or-v4
s3proxy.identity=local-identity
s3proxy.credential=local-credential
s3proxy.keystore-path=/tmp/keystore.jks
s3proxy.keystore-password=password

jclouds.provider=transient
jclouds.identity=remote-identity
jclouds.credential=remote-credential
Prefer HTTPS links in documentation where possible This also corrects a test URL which was HTTPS in practice. 2019-04-05 16:24:59 +09:00			`s3proxy.secure-endpoint=https://127.0.0.1:8080`
Individually test multiple s3fs flags Remove unneeded comments; single part limits ensure that the tests exercise multipart code paths even with smaller files. References #971. 2019-06-12 16:35:26 -07:00			`s3proxy.authorization=aws-v2-or-v4`
Use s3proxy to run integration tests References #129. 2015-02-24 05:17:59 -08:00			`s3proxy.identity=local-identity`
			`s3proxy.credential=local-credential`
Generate S3Proxy SSL certificate during tests (#1845) Also provide CA bundle to AWS CLI to work around CI failures instead of ignoring errors. Fixes #1812. 2022-01-09 15:13:36 +09:00			`s3proxy.keystore-path=/tmp/keystore.jks`
Configure S3Proxy for SSL This also demonstrates that SSL certificate checking occurs and the tests must disable it for S3Proxy's self-signed certificate. References #640. 2017-09-17 16:14:58 -07:00			`s3proxy.keystore-password=password`
Use s3proxy to run integration tests References #129. 2015-02-24 05:17:59 -08:00
			`jclouds.provider=transient`
			`jclouds.identity=remote-identity`
			`jclouds.credential=remote-credential`