-
Notifications
You must be signed in to change notification settings - Fork 96
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 requestPayment and lifecycle stub callbacks [JIRA: RCS-272] #1223
Conversation
In order to response a little more understandable response. For requestPayment, just reply XML with "BucketOwner" after authn/authz. For lifecycle, just reply error XML of "NotImplemented" without anthentication.
@@ -71,9 +71,13 @@ base_resources() -> | |||
{["buckets", bucket, "objects"], riak_cs_wm_common, props(riak_cs_wm_objects)}, | |||
{["buckets", bucket, "delete"], riak_cs_wm_common, props(riak_cs_wm_bucket_delete)}, | |||
{["buckets", bucket, "acl"], riak_cs_wm_common, props(riak_cs_wm_bucket_acl)}, | |||
%% Just stub, no dynamic contents | |||
{["buckets", bucket, "location"], riak_cs_wm_common, props(riak_cs_wm_bucket_location)}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
location is no more a stub because it's return value is configurable via configuration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, reasonable :) I did so just because location does not have meaning anywhere else in riak cs (except a possibility of v4 auth.)
Updated. |
…cycle-stub Add requestPayment and lifecycle stub callbacks Reviewed-by: kuenishi
@borshop merge |
Release note: Add 501 stub for Bucket lifecycle and simple stub for Bucket requestPayment _[posted via JIRA by Kota Uenishi]_ |
Before this PR,
lifecycle
is notincluded in subresources definition of Riak CS.
In order to response a little more understandable response, this PR changes them as:
To be truthful, motivation for these changes were from s3cmd error for
s3cmd info <bucket>
㊙️