-
Notifications
You must be signed in to change notification settings - Fork 0
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 Google Cloud Storage Source e2e test #124
Conversation
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.
The test looks primarily good. Do have one question that should be addressed before blessing the PR.
// CreateObject creates an object named after the given framework.Framework. | ||
func CreateObject(storageCli *storage.Client, project string, bucket string, f *framework.Framework) string { | ||
object := f.UniqueName | ||
file, err := os.Create("/tmp/" + object) |
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 see the file being created, but where is it being deleted?
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.
@cab105 I just added the file deletion.
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 need to delete though? I haven't looked at the code yet, but I would expect that we simply
- Create a bucket
- Create a file
- Delete the bucket
similarly to other tests (GitHub, etc.)
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.
We do in this case as the file is created locally first, and then uploaded to GCP. Since these tests can run locally we need to clean up our mess instead of relying on a higher power to do it for us (whether it is in docker or reboot on some unix based systems).
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.
Oh, didn't understand it that way :) Thanks for the clarification!
Closes #123