Skip to content

Investigate GCS destination integration test failure #9631

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

Closed
tuliren opened this issue Jan 20, 2022 · 2 comments · Fixed by #10299
Closed

Investigate GCS destination integration test failure #9631

tuliren opened this issue Jan 20, 2022 · 2 comments · Fixed by #10299
Assignees
Labels
area/connectors Connector related issues type/bug Something isn't working

Comments

@tuliren
Copy link
Contributor

tuliren commented Jan 20, 2022

The integration test passed locally, but failed on CI (attempt).

@tuliren
Copy link
Contributor Author

tuliren commented Feb 11, 2022

The current hypothesis:

  1. The sync command only needs 6 permissions, as listed in the doc.
  2. The connection check command, however, requires 2 more permissions (multipartUpload.list and multipartUpload.listAll), which is incorrect. So the check tests are failing in the acceptance test.

Next step:

  1. Confirm the above hypothesis.
  2. Fix the connection check command so that it does not need the two extra permission to pass.
  3. If there is no way to fix the connection check, either remove the check that requires the extra permission, or list the two extra permission on the doc (not ideal).

@tuliren
Copy link
Contributor Author

tuliren commented Feb 13, 2022

This issue has been fixed in version 0.1.21. Now only the permissions listed in the doc are needed to sync data to GCS:

storage.multipartUploads.abort
storage.multipartUploads.create
storage.objects.create
storage.objects.delete
storage.objects.get
storage.objects.list

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connectors Connector related issues type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant