Commit Graph

22 Commits

Author SHA1 Message Date
Krzysztof Wilczynski f5b46b80e7 Add ability to set canned ACL in aws_s3_bucket_object. (#8091)
An S3 Bucket owner may wish to set a canned ACL (as opposite to explicitly set
grantees, etc.) for an object. This commit adds an optional "acl" attribute to
the aws_s3_bucket_object resource so that the owner of the S3 bucket can
specify an appropriate pre-defined ACL to use when creating an object.

Signed-off-by: Krzysztof Wilczynski <krzysztof.wilczynski@linux.com>
2016-08-10 16:05:39 +12:00
Kraig Amador 76b3c74a58 Providing a more informative error message when combining kms_key_id and etag as well as using aws_kms_key to test aws_s3_bucket's kms_key_id. 2016-03-09 19:06:36 -08:00
Kraig Amador 74de6531fe Return an error when conflicting etag & kms_key_id parameters are provided and now with ServerSideEncryption we can go back to the higher level PutObject. 2016-03-04 09:22:43 -08:00
Kraig Amador db91aebd8e Added a kms_key_id parameter which will allow you to encrypt objects that are put into a bucket. 2016-03-03 16:20:01 -08:00
Radek Simko 24ac996963 provider/aws: Add support for versioned objects 2016-02-25 12:04:18 +00:00
Radek Simko 2f8b9edaf8 provider/aws: Add support for s3_bucket_object updates 2016-02-25 12:04:16 +00:00
Radek Simko ebf2fd54e5 provider/aws: Clean up whitespaces 2016-02-24 14:58:17 +00:00
Radek Simko 70f045e46e provider/aws: Breaking change - Trim off quotes for aws_s3_bucket_object.etag 2016-02-24 14:58:17 +00:00
Paul Hinze 44f259bd74 provider/aws: homedir expand in s3 object source
fixes #3856
2015-11-13 11:21:22 -06:00
stack72 3809cb5b88 Fixing the merge conflicts on the s3 bucket object resource after another PR had been merged 2015-10-12 16:51:27 +01:00
Martin Atkins a888cd6f62 Merge pull request #3200 from zpatrick/master
Optional "content" argument for "s3_bucket_object"
2015-10-10 11:26:38 -07:00
stack72 080e08fb73 Adding Computed to the Content-Type of S3 Bucket Object. Regardless of whether you set a content-type, AWS will always set a content-type 2015-10-08 23:14:34 +01:00
stack72 b3010e1412 Because of the lack of Update, S3 Bucket Object needs to force new when changing the params 2015-10-08 18:50:30 +01:00
stack72 8e2163c963 Removing the S3 Bucket Object Update method. This was removed in master but seems to be broken in my branch 2015-10-08 18:44:59 +01:00
stack72 0a5387db90 Adding some examples of the S3 bucket object parameters as well as checking for an empty string in the new S3 bucket object params 2015-10-08 17:24:33 +01:00
Radek Simko 9cbcb9a438 Remove no-op Updates from resource schemas 2015-10-03 14:29:19 -07:00
stack72 2b7a13b609 Adding some other simple S3 Bucket Object (Optional) Inputs 2015-09-17 20:13:06 +01:00
zpatrick 5256a6df6b fix formatting 2015-09-10 18:37:17 +00:00
zpatrick 03f94d66ae adding content field to s3_bucket_object 2015-09-09 21:13:36 +00:00
Clint Shryock bfaea76b86 more tightly scope s3 bucket object error 2015-08-05 14:27:34 -05:00
Clint Shryock 44f470514c provider/aws: Add S3 Bucket Object (supercedes #2079) 2015-07-30 15:17:37 -05:00
Michael Austin 9a8625e6a6 added new provider for creating objects in an s3 bucket 2015-05-26 10:46:06 -04:00