-
Notifications
You must be signed in to change notification settings - Fork 21
remove opaque parameters from delete request and return bucket id o… #25
Conversation
…n succesful bucket creation
cosi.proto
Outdated
// Intentionally left blank | ||
// BucketName returned here is expected to be the globally unique | ||
// identifier for the bucket in the object storage provider | ||
string BucketName = 1; |
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.
do we want BucketName here or BucketID?
I thought the response was going to return the full bucket id.
} | ||
|
||
message ProvisionerDeleteBucketRequest { | ||
// This field is REQUIRED | ||
// Protocol specific information required by the call is passed in as key,value pairs. | ||
Protocol protocol = 1; | ||
|
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.
don't we need the bucket id? How does the provisoner know which bucket to delete?
// Protocol specific information required by the call is passed in as key,value pairs. | ||
// The caller should treat the values in parameters as opaque. | ||
// The receiver is responsible for parsing and validating the values. | ||
map<string,string> parameters = 2; |
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.
In ProvisionerDeleteBucketResponse (L200) should access_policy = 1 (not 4)?
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.
In ProvisionerGrantBucketAccessRequest (L204), I thought that protocol and parameters were being removed. Also where is the id of the bucket for which access is requested? I think we need bucketID or bucketName.
@@ -239,13 +235,9 @@ message ProvisionerRevokeBucketAccessRequest { | |||
// Protocol specific information required by the call is passed in as key,value pairs. | |||
Protocol protocol = 1; | |||
|
|||
// This field is OPTIONAL |
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.
Same comment as above. I thought protocol was being removed. I also think we need the bucket id so that the driver knows which bucket to revoke access to.
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.
Yes, that's correct. I've updated the PR
5e48ef4
to
c0c84e3
Compare
lgtm |
cosi.proto
Outdated
// be required later to revoke access. | ||
string principal = 1; | ||
string accountID = 1; |
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.
accountID seems more intuitive and also is symmetric with bucketID
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.
Ack. I don't have the context on this, maybe worth having someone else who was part of that discussion take a look
48f7904
to
6f5e0e4
Compare
- Use BucketID returned from ProvisionerCreateBucket as the handle for subsequent bucket related gRPC calls - Remove Name and Version from Protocol
- Requires changes to API from this PR kubernetes-retired/container-object-storage-interface-api#35 - Requires changes to SPEC from this PR kubernetes-retired/container-object-storage-interface-spec#25
- Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-api/pull/35 - Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-spec/pull/25
- Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-api/pull/35 - Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-spec/pull/25
- Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-api/pull/35 - Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-spec/pull/25
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.
LGTM mod accountName
(I wasn't involved in the discussion to replace principal
with accountName
, so I'll assume those were discussed with the wider community).
spec.md
Outdated
S3Parameters s3 = 1; | ||
AzureBlobParameters azureBlob = 2; | ||
GCSParameters gcs = 3; |
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.
nit: why suffix these with Parameters
?
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.
Protocol name S3 otherwise collides with the Parameter type S3
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.
Do you mean it collides with enum ProtocolName
? if so, is that enum still needed (it is removed in this PR)?
Yeah, this was discussed with the community and accepted |
509238b
to
8d93410
Compare
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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saad-ali, wlan0 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
- Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-api/pull/35 - Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-spec/pull/25
- Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-api/pull/35 - Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-spec/pull/25
- Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-api/pull/35 - Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-spec/pull/25
- Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-api/pull/35 - Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-spec/pull/25
- Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-api/pull/35 - Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-spec/pull/25
- Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-api/pull/35 - Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-spec/pull/25
- Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-api/pull/35 - Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-spec/pull/25
- Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-api/pull/35 - Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-spec/pull/25
- Requires changes to API from this PR github.com/kubernetes-retired/pull/35 - Requires changes to API from this PR github.com/kubernetes-retired/container-object-storage-interface-spec/pull/25
…n succesful bucket creation.