Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
I'm told SkySQL will be running on Google's cloud, so at some point we need to verify storagemanager works there. In theory it's S3 compat and in theory this-that-and-the-other, but we need to see that it actually does work there as expected.
I'm guessing the test + bureaucracy will take 1d unless we find a compat issue.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link |
|
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Stalled [ 10000 ] |
| Rank | Ranked higher |
| Status | Stalled [ 10000 ] | In Progress [ 3 ] |
Andrew patched up the s3 lib, which allowed testing. Looks like there's no compat issue.
| issue.field.resolutiondate | 2019-08-20 18:46:19.0 | 2019-08-20 18:46:19.446 |
| Component/s | ? [ 14509 ] | |
| Fix Version/s | 1.4.0 [ 23256 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
Doesn't work yet, gets 'The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method.' on attempting to put a test file.
I did the sanity checks I can (verified no errors in the keys, region, bucket, etc), and turned the dials available to the dev through the s3 lib, seems like it's probably a compat issue with the s3 lib. Notified Andrew; he will investigate further when he can.