-
Notifications
You must be signed in to change notification settings - Fork 499
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
S3 provider always uses us-east-1 #8
Comments
Awesome, I am happy to confirm this S3 issue is resolved - also the other commit which resolved the access key panic. |
erezrokah
pushed a commit
that referenced
this issue
Aug 14, 2022
🤖 I have created a release *beep* *boop* --- ## [0.0.3](https://github.com/cloudquery/cq-provider-fuzz/compare/v0.0.2...v0.0.3) (2022-06-26) ### Bug Fixes * **deps:** Update module github.com/cloudquery/cq-provider-sdk to v0.12.2 ([#7](https://github.com/cloudquery/cq-provider-fuzz/issues/7)) ([f9d3e92](https://github.com/cloudquery/cq-provider-fuzz/commit/f9d3e92df35131c0ca8229c60f1d7387d30210e9)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
erezrokah
pushed a commit
that referenced
this issue
Aug 14, 2022
* initial commit update github provider * goimports * add tables * add team repos * add issues * add billing tables * add organizations installations * add organizations installations * adding hook resource * add mock services * start adding mock tests * fix imports * more tests * external groups mock tests * finish up tests * update table docs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am not sure wether this change was correct:
c6cddae#diff-ec36749d97d730e19702baa9729041e766dd4134df981ae67702657c0abd515b
Because in 0.4.2 I get this when fetching s3 buckets:
The text was updated successfully, but these errors were encountered: