Closed snarlysodboxer closed 2 years ago
These are the Connect server logs from running the above code. Note the Invalid Item UUID
towards the middle, which is strange because it doesn't seem to line up with when the SDK returns the error. Nor is there a matching request ID for that one.
I've used search and replace to redact various things, but replaced them with identical identifiers.
{"log_message":"(I) GET /v1/vaults?filter=title+eq+%22my-vault%22","timestamp":"2022-07-01T23:55:37.394518085Z","level":3,"scope":{"request_id":"c4e4e254-67d6-4f88-a540-5fdce5285360"}}
{"log_message":"(I) GET /v1/vaults?filter=title+eq+%22my-vault%22 completed (200: OK)","timestamp":"2022-07-01T23:55:37.400141881Z","level":3,"scope":{"request_id":"c4e4e254-67d6-4f88-a540-5fdce5285360","jti":"wa3czmoxz-redacted"}}
{"log_message":"(I) GET /v1/vaults/my-vault-redacted-id/items?filter=title+eq+%22docker-credentials%22","timestamp":"2022-07-01T23:55:37.401812101Z","level":3,"scope":{"request_id":"c5745418-04f4-4f02-b1c5-fc237e0e06f8"}}
{"log_message":"(I) GET /v1/vaults/my-vault-redacted-id/items?filter=title+eq+%22docker-credentials%22 completed (200: OK)","timestamp":"2022-07-01T23:55:37.408569326Z","level":3,"scope":{"request_id":"c5745418-04f4-4f02-b1c5-fc237e0e06f8","jti":"wa3czmoxz-redacted"}}
{"log_message":"(E) 400: Invalid Item UUID","timestamp":"2022-07-01T23:55:37.409201998Z","level":1,"scope":{"request_id":"becd2c94-6677-42a9-a0a7-2d5f9110c7af","jti":"wa3czmoxz-redacted"}}
{"log_message":"(I) GET /v1/vaults/my-vault-redacted-id/items/my-item-redacted-id","timestamp":"2022-07-01T23:55:37.410504804Z","level":3,"scope":{"request_id":"004ad656-74d8-429d-a160-b8dd2c45cc08"}}
{"log_message":"(I) GET /v1/vaults/my-vault-redacted-id/items/my-item-redacted-id completed (200: OK)","timestamp":"2022-07-01T23:55:37.416893787Z","level":3,"scope":{"request_id":"004ad656-74d8-429d-a160-b8dd2c45cc08","jti":"wa3czmoxz-redacted"}}
{"log_message":"(I) GET /v1/vaults/my-vault-redacted-id/items/my-item-redacted-id","timestamp":"2022-07-01T23:55:37.418238425Z","level":3,"scope":{"request_id":"09e83f12-e2af-4017-b9d2-3873d1e2c960"}}
{"log_message":"(I) GET /v1/vaults/my-vault-redacted-id/items/my-item-redacted-id completed (200: OK)","timestamp":"2022-07-01T23:55:37.424186677Z","level":3,"scope":{"request_id":"09e83f12-e2af-4017-b9d2-3873d1e2c960","jti":"wa3czmoxz-redacted"}}
I noticed that if I manually add the ContentPath
to the file object before passing it to GetFileContents
, it worked. This is because Connect Server v1.5.4 is sending contentPath
but the code is looking for content_path
. Here's a PR to fix the client, but you may want to fix the Connect Server instead? https://github.com/1Password/connect-sdk-go/pull/65
I tried a variation of the above code using GetFiles
in place of GetVaultsByTitle
+ GetItemsByTitle
, and it also happens to be broken for a different reason, a typo. Here's a PR for that: https://github.com/1Password/connect-sdk-go/pull/64
Hey @snarlysodboxer. Thank you for reporting this! We are working on addressing this in the Connect server.
In the meantime, we recommend downgrading the API container to v1.5.3. You can leave the sync container at 1.5.4 (which should address #36).
@jpcoenen Thanks. FWIW, simply downgrading isn't sufficient because of the above mentioned bug in the connect-sdk-go. (The fix has been merged, but a new release has not been cut.)
In the meantime the 1Password integration for external-secrets is broken for anyone using Document type items.
Hey @snarlysodboxer, We've just released Connect Go SDK v1.5.0 which does include the fix you're looking for. 😊
Hey there again!
Good news! We've just released v1.5.5 of the Connect server which addresses the content_path
bug for File object.
Thank you again for reporting this bug.
Great!! Thank you!
Hi, As shared here, I am having the error with v1.5.6
Would you know what is wrong?
Docker images:
1password/connect-api:1.5.4
and1password/connect-sync:1.5.4
. Connect-sdk-go version:v1.4.0
.With
1.5.0
of Connect, the following code worked, but with1.5.4
it producesHere's the code to repeat the problem: