chore: regenerate SDK from latest API spec - #193
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (59)
📒 Files selected for processing (5)
WalkthroughThe management SDK was regenerated with additional directory, organization invite, passkey, permission, update, and identity artifacts. Package exports and API exposure tests were expanded, while generator and SDK version metadata changed from 2.0.0 to 2.3.0. ChangesManagement SDK regeneration
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
I am busy with a regression test on these changes currently |
|
Live-tested the new organization invite listing endpoint successfully: The endpoint requires Allow invitations to be enabled with an interactive Invite application selected. An M2M application cannot be selected for that purpose, although its credentials are still used to call the Management API. After configuring both applications, the generated SDK call and response deserialization passed. |
|
Live-test finding: create_directory() creates the resource but returns 409 The new DirectoriesApi.create_directory() method sends one POST: but returns: The generated client correctly expects 201 CreateDirectoryResponse, matching the OpenAPI spec. Despite returning 409, the backend creates the directory. Subsequent get, list, update, and delete calls all succeeded. This appears to be a backend responseissue rather than a generated Python SDK defect, but it prevents callers from receiving the successful create response through this new PR API. Not sure if a backend management fix should be applied by the Kinde team?? |
|
Tests completed Completed Directory read/get/update/delete Organization invite create/get/list/delete Environment and organization passkeys System permissions, role permissions, and role users Organization response fields User identity deserialization Environment response fields Stress, cleanup, redaction, and harness validation Outstanding API finding |
|
PBKDF2 password import MFA recovery-code settings Organization MFA was skipped due to the tenant plan. Environment MFA was not mutated because no GET endpoint supports safe restoration. Organization model updates Connection option changes SDK version metadata Final management-suite verification Result: 105 passed |
|
Explain your changes
Syncs the generated management client with the live management API spec
Checklist
🛟 If you need help, consider asking for advice over in the Kinde community.