Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix prepared a fix for the issue found in the latest run.
- ✅ Fixed: Whoami drops most user config fields silently
- Updated
whoamito passoptions?.configdirectly intocreateIAMClient, preserving all user-provided IAM config fields.
- Updated
Or push these changes by commenting:
@cursor push f6fef5bd5f
Preview (f6fef5bd5f)
diff --git a/packages/iam/src/lib/whoami.ts b/packages/iam/src/lib/whoami.ts
--- a/packages/iam/src/lib/whoami.ts
+++ b/packages/iam/src/lib/whoami.ts
@@ -18,13 +18,7 @@
export async function whoami(
options?: WhoamiOptions
): Promise<TigrisIAMResponse<WhoamiResponse, Error>> {
- const { data: client, error } = createIAMClient(
- {
- sessionToken: options?.config?.sessionToken,
- },
- true,
- true
- );
+ const { data: client, error } = createIAMClient(options?.config, true, true);
if (error) {
return { error };This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.
Greptile SummaryThis PR implements a Confidence Score: 4/5Safe to merge after fixing the partial config forwarding in The overall design is sound and consistent with the rest of the IAM package. There is one concrete P1 bug: caller-provided credential and endpoint fields in
Important Files Changed
Reviews (1): Last reviewed commit: "feat(iam): implement whoami" | Re-trigger Greptile |
|
🎉 This PR is included in version 1.4.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.15.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |


Note
Medium Risk
Adds a new
whoamicall and extends client configuration/authentication inputs (including askipCheckpath) which could change how requests are authorized if misused, though scope is limited to IAM client wiring.Overview
Adds a new
whoamiAPI (GET /users/whoami) to the IAM package and exports it from the publicindex.ts, returning the currentuserIdandorganizationId.Extends IAM config/client creation to accept
accessKeyId/secretAccessKey(loaded fromTIGRIS_STORAGE_ACCESS_KEY_ID/TIGRIS_STORAGE_SECRET_ACCESS_KEY) and introduces an optionalskipCheckflag to bypass requiredsessionToken/organizationIdvalidation when creating an IAM client.Includes a small tweak to shared HTTP client error construction (formatting-only).
Written by Cursor Bugbot for commit 80de209. This will update automatically on new commits. Configure here.