-
Notifications
You must be signed in to change notification settings - Fork 807
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
Implementing ListSnapshots #286
Conversation
Hi @zacharya. Thanks for your PR. I'm waiting for a kubernetes-sigs or kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Pull Request Test Coverage Report for Build 623
💛 - Coveralls |
/ok-to-test |
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.
Overall LGTM. Left some comments. Also could you add some details on how is this being tested?
pkg/cloud/cloud.go
Outdated
func (c *cloud) ListSnapshots(ctx context.Context, volumeID string, maxResults int64, nextToken string) (listSnapshotsResponse *ListSnapshotsResponse, err error) { | ||
describeSnapshotsInput := &ec2.DescribeSnapshotsInput{} | ||
|
||
if maxResults >= 5 { |
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.
Since controller.ListSnapshots
already has logic to guarantee maxResults >= 5
, as cloud
is an internal struct, I feel we can just set describeSnapshotsInput.MaxResults = aws.Int64(maxResults)
without checking if maxResults >= 5 {
.
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.
I just pushed another commit that enabled ListSnapshot sanity testing. In order to satisfy the unit tests from the sanity testing packages, I had to push the logic down into the cloud
package so controller was able to handle 0 < MaxEntries
< 5. Let me know how you want to proceed with this. It's mostly cosmetic as we're just using fakeCloudProvider
anyways.
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.
If that's what the sanity test checks, im okay with the change.
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: leakingtapan, zacharya 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 |
/retest |
1 similar comment
/retest |
Is this a bug fix or adding new feature?
Fixes: #233
What is this PR about? / Why do we need it?
This implements ListSnapshots from the CSI spec (not yet used by Kubernetes).
What testing is done?
Unit tests have been written for
driver
andcloud
packages that handle both happy path and error cases.