-
Notifications
You must be signed in to change notification settings - Fork 9.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to set Storage Class in aws_s3_bucket_object. #8174
Add ability to set Storage Class in aws_s3_bucket_object. #8174
Conversation
1a7e460
to
f8052a8
Compare
An S3 Bucket owner may wish to select a different underlying storage class for an object. This commit adds an optional "storage_class" attribute to the aws_s3_bucket_object resource so that the owner of the S3 bucket can specify an appropriate storage class to use when creating an object. Signed-off-by: Krzysztof Wilczynski <[email protected]>
f8052a8
to
95fc7fe
Compare
Tests are passing:
|
@stack72 over to you 🚀 |
Hey @kwilczynski Thanks for the PR here :) Unfortunately, the P. |
@stack72 thank you for looking at the code. I can see it being set to both Computed and Optional in the commit, as per: "storage_class": &schema.Schema{
Type: schema.TypeString,
Optional: true,
Computed: true,
ValidateFunc: validateS3BucketObjectStorageClassType,
}, (commit: resource_aws_s3_bucket_object.go#L85-L90) While testing, it seem to be working fine:
(saved execution log for the above): If there is something wrong, I am happy to correct it. Let me know :) |
@kwilczynski that's so odd - looks like for some reason - I cou;dnt see that locally at first glance. I'm blaming jetlag :) Tests look good to me!
Thanks :) Paul |
…8174) An S3 Bucket owner may wish to select a different underlying storage class for an object. This commit adds an optional "storage_class" attribute to the aws_s3_bucket_object resource so that the owner of the S3 bucket can specify an appropriate storage class to use when creating an object. Signed-off-by: Krzysztof Wilczynski <[email protected]>
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
An S3 Bucket owner may wish to select a different underlying storage class
for an object. This commit adds an optional "storage_class" attribute to the
aws_s3_bucket_object resource so that the owner of the S3 bucket can specify
an appropriate storage class to use when creating an object.
Signed-off-by: Krzysztof Wilczynski [email protected]