Skip to content
This repository was archived by the owner on Dec 3, 2024. It is now read-only.

remove opaque parameters from delete request and return bucket id o… #25

Merged
merged 3 commits into from
Mar 29, 2021

Conversation

wlan0
Copy link
Contributor

@wlan0 wlan0 commented Mar 4, 2021

…n succesful bucket creation.

@wlan0 wlan0 requested a review from saad-ali March 4, 2021 06:54
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Mar 4, 2021
@k8s-ci-robot k8s-ci-robot requested review from msau42 and xing-yang March 4, 2021 06:55
@k8s-ci-robot k8s-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Mar 4, 2021
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;
Copy link

@jeffvance jeffvance Mar 10, 2021

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;

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;

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)?

Copy link

@jeffvance jeffvance Mar 10, 2021

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

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.

Copy link
Contributor Author

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

@k8s-ci-robot k8s-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Mar 17, 2021
@wlan0 wlan0 force-pushed the master branch 2 times, most recently from 5e48ef4 to c0c84e3 Compare March 25, 2021 15:57
@jeffvance
Copy link

lgtm

@wlan0 wlan0 changed the title remove opaque parameters from delete request and return bucket name o… remove opaque parameters from delete request and return bucket id o… Mar 25, 2021
cosi.proto Outdated
// be required later to revoke access.
string principal = 1;
string accountID = 1;
Copy link
Contributor Author

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

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

@wlan0 wlan0 force-pushed the master branch 2 times, most recently from 48f7904 to 6f5e0e4 Compare March 26, 2021 20:38
 - Use BucketID returned from ProvisionerCreateBucket as the handle for subsequent bucket related gRPC calls
 - Remove Name and Version from Protocol
wlan0 added a commit to wlan0/container-object-storage-interface-provisioner-sidecar that referenced this pull request Mar 26, 2021
wlan0 added a commit to wlan0/container-object-storage-interface-provisioner-sidecar that referenced this pull request Mar 26, 2021
 - 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
wlan0 added a commit to wlan0/container-object-storage-interface-provisioner-sidecar that referenced this pull request Mar 26, 2021
 - 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
wlan0 added a commit to wlan0/container-object-storage-interface-provisioner-sidecar that referenced this pull request Mar 26, 2021
 - 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
Copy link

@saad-ali saad-ali left a 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
Comment on lines 270 to 272
S3Parameters s3 = 1;
AzureBlobParameters azureBlob = 2;
GCSParameters gcs = 3;

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?

Copy link
Contributor Author

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

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)?

@wlan0
Copy link
Contributor Author

wlan0 commented Mar 29, 2021

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).

Yeah, this was discussed with the community and accepted

@k8s-ci-robot k8s-ci-robot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Mar 29, 2021
@wlan0 wlan0 force-pushed the master branch 2 times, most recently from 509238b to 8d93410 Compare March 29, 2021 22:46
Copy link

@saad-ali saad-ali left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 29, 2021
@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 29, 2021
@k8s-ci-robot k8s-ci-robot merged commit 3bbacbb into kubernetes-retired:master Mar 29, 2021
wlan0 added a commit to wlan0/container-object-storage-interface-provisioner-sidecar that referenced this pull request Mar 31, 2021
 - 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
wlan0 added a commit to wlan0/container-object-storage-interface-provisioner-sidecar that referenced this pull request Mar 31, 2021
 - 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
wlan0 added a commit to wlan0/container-object-storage-interface-provisioner-sidecar that referenced this pull request Mar 31, 2021
 - 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
wlan0 added a commit to wlan0/container-object-storage-interface-provisioner-sidecar that referenced this pull request Mar 31, 2021
 - 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
wlan0 added a commit to wlan0/container-object-storage-interface-provisioner-sidecar that referenced this pull request Apr 5, 2021
 - 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
wlan0 added a commit to wlan0/container-object-storage-interface-provisioner-sidecar that referenced this pull request Apr 5, 2021
 - 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
wlan0 added a commit to wlan0/container-object-storage-interface-provisioner-sidecar that referenced this pull request Apr 6, 2021
 - 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
wlan0 added a commit to wlan0/container-object-storage-interface-provisioner-sidecar that referenced this pull request Apr 6, 2021
 - 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
shanduur pushed a commit to shanduur/container-object-storage-interface-api that referenced this pull request Jun 6, 2024
 - 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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants