[FIX] - Update Azure LLM adapter to use deployment name as model name#1690
[FIX] - Update Azure LLM adapter to use deployment name as model name#1690
Conversation
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings. WalkthroughThis change bumps tool versions across the Unstract platform: Structure Tool from 0.0.91 to 0.0.92, Classifier Tool from 0.0.71 to 0.0.72, and Text Extractor Tool from 0.0.67 to 0.0.68. Additionally, the Azure OpenAI LLM adapter validation logic is updated to derive the model prefix from Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Pre-merge checks and finishing touches❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (1 passed)
✨ Finishing touches
🧪 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 |
Test ResultsSummary
Runner Tests - Full Report
SDK1 Tests - Full Report
|
|
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to Reviews > Disable Cache setting
Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting
📒 Files selected for processing (6)
backend/sample.env(1 hunks)tools/classifier/src/config/properties.json(1 hunks)tools/structure/src/config/properties.json(1 hunks)tools/text_extractor/src/config/properties.json(1 hunks)unstract/sdk1/src/unstract/sdk1/adapters/base1.py(1 hunks)unstract/tool-registry/tool_registry_config/public_tools.json(3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: build
🔇 Additional comments (6)
tools/classifier/src/config/properties.json (1)
5-5: Metadata version update is consistent with registry.The toolVersion bump from 0.0.71 to 0.0.72 aligns with parallel updates in public_tools.json and is a metadata-only change.
tools/structure/src/config/properties.json (1)
5-5: Metadata version update is consistent with environment config.The toolVersion bump from 0.0.91 to 0.0.92 aligns with updates in backend/sample.env and is a metadata-only change.
tools/text_extractor/src/config/properties.json (1)
5-5: Metadata version update is consistent with registry.The toolVersion bump from 0.0.67 to 0.0.68 aligns with parallel updates in public_tools.json and is a metadata-only change.
backend/sample.env (1)
92-94: Environment configuration updates are consistent with tool version bump.The Structure Tool image URL and tag both reference version 0.0.92, aligning with the properties.json update. These are configuration-only changes.
unstract/tool-registry/tool_registry_config/public_tools.json (2)
8-8: Classifier tool registry metadata is consistent.The toolVersion, image_url, and image_tag all reference version 0.0.72, matching the individual tool properties.json update.
Also applies to: 109-111
119-119: Text Extractor tool registry metadata is consistent.The toolVersion, image_url, and image_tag all reference version 0.0.68, matching the individual tool properties.json update.
Also applies to: 194-196



What
Why
How
Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)
Database Migrations
Env Config
Relevant Docs
Related Issues or PRs
Dependencies Versions
Notes on Testing
Screenshots
Checklist
I have read and understood the Contribution Guidelines.