:cloud:Amazon S3-based resolver for sbt
#57: Changed awsProfile
type to Option[String]
and changed s3region
and s3credentials
defaults to depend on it (by @tsuyoshizawa):
By default awsProfile
is set to None
which means that both region and credentials will be set from the default provider chains.
And if you change it, s3region
and s3credentials
will both use given profile region and credentials.
This makes these two settings more consistent, but also introduces a potentially breaking change: if you used some unusual setting for s3region
or s3credentials
, check their values after this update:
> show s3region
> showS3Credentials
This release also deprecates conversions related to credential providers: |
for chaining and implicit conversion from File
. Use AWS Java SDK explicitly instead.
s3acl
type to Option[S3ACL]
: when it's unset, artifacts will be published inheriting the bucket ACL (by @hkupty)This is a bugfix release, it updates to ivy-s3-resolver v0.12.0 which solves the problem with redundant delimiters the ivy-style patterns introduced in sbt 1.0 (see sbt/sbt#3573).
The problem was reported and handled in the underlying library by Michael Ahlers @michaelahlers:
This release is affected by the problem with redundant delimiters in the ivy-style patterns introduced in sbt 1.0 (see sbt/sbt#3573). You are strongly recommended to update to the next version which contains a fix for it.
toHttps
method works for different regions with different endpoint prefixescom.amazonaws.regions.Region
DefaultAwsRegionProviderChain
; added implicit conversionsv0.9.0
project/plugins.sbt
and enjoy~/.aws/credentials
(same as you use form AWS command line tools). You can choose profile by setting awsProfile
key.s3acl
Access Control List configuration parameter (which defaults to PublicRead
) (thanks @anzecesar, see #36)v0.6.0
. See ohnosequences/sbt-s3-resolver#31.