UN-2427 [FEAT]: Dynamically override LLM Profile in API Deployment invocation#1388
Merged
vishnuszipstack merged 14 commits intomainfrom Jul 4, 2025
Conversation
… override - from api deployment - Add end-to-end llm_profile_id propagation from API deployment to workflow execution - Implement profile-based tool settings override in structure tool with detailed change tracking - Add ownership validation to ensure only profile owners can use their profiles - Fix platform service helper to use correct profile_id column name - Update SDK integration with profile support branch and AWS dependencies - Add comprehensive logging for profile propagation and override debugging - Enhance structure tool with profile override methods and change reporting - Propagate llm_profile_id through FileData, workflow execution, and metadata storage - Add profile override mapping for chunk settings, LLM, embedding, vector DB, and x2text adapters - Include detailed before/after logging for tool metadata changes This enables dynamic tool configuration based on user-defined LLM profiles, allowing users to override tool settings like LLM models, embeddings, and processing parameters at runtime while maintaining backward compatibility and comprehensive audit logging.
vishnuszipstack
requested review from
Deepak-Kesavan,
athul-rs,
chandrasekharan-zipstack,
jagadeeswaran-zipstack,
jaseemjaskp,
johnyrahul and
muhammad-ali-e
and removed request for
chandrasekharan-zipstack
Contributor
chandrasekharan-zipstack
left a comment
chandrasekharan-zipstack
left a comment
There was a problem hiding this comment.
@vishnuszipstack it wasn't obvious from the screenshots but I thought that the Copy icon meant duplicating a profile. I think it might confuse users.
I suggest that we display the llm_profile_id (profile_id) against every record (as a greyed out text under the profile name maybe). We can have a little copy icon too next to it
Contributor
|
@vishnuszipstack also ensure that the postman collection and our public docs is updated with this parameter |
vishnuszipstack
requested review from
chandrasekharan-zipstack and
muhammad-ali-e
chandrasekharan-zipstack
approved these changes
Jul 3, 2025
Contributor
chandrasekharan-zipstack
left a comment
chandrasekharan-zipstack
left a comment
There was a problem hiding this comment.
LGTM - left a minor concern around moving this validation of llm_profile_id into the serializer or by making use of DRF's permissions
…api-deployment-invocation
…-profile-in-api-deployment-invocation' into UN-2427-dynamically-override-llm-profile-in-api-deployment-invocation
Contributor
|
|
vishnuszipstack
deleted the
UN-2427-dynamically-override-llm-profile-in-api-deployment-invocation
branch
pk-zipstack
pushed a commit
that referenced
this pull request
Aug 20, 2025
…vocation (#1388) * FEAT: implement complete LLM profile ID propagation and tool settings override - from api deployment - Add end-to-end llm_profile_id propagation from API deployment to workflow execution - Implement profile-based tool settings override in structure tool with detailed change tracking - Add ownership validation to ensure only profile owners can use their profiles - Fix platform service helper to use correct profile_id column name - Update SDK integration with profile support branch and AWS dependencies - Add comprehensive logging for profile propagation and override debugging - Enhance structure tool with profile override methods and change reporting - Propagate llm_profile_id through FileData, workflow execution, and metadata storage - Add profile override mapping for chunk settings, LLM, embedding, vector DB, and x2text adapters - Include detailed before/after logging for tool metadata changes This enables dynamic tool configuration based on user-defined LLM profiles, allowing users to override tool settings like LLM models, embeddings, and processing parameters at runtime while maintaining backward compatibility and comprehensive audit logging. * removed unwanted file * pr comment fixes * added llm id below to name and moved copy button * moved llm profile id ownership validation to serializer * pr comment fixes and removed unwanted code in frontend sonar fix * sdk version bump up * Commit uv.lock changes * sdk version bump up in other places * Commit uv.lock changes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note:-
What
Implemented end-to-end LLM Profile ID propagation from API deployment to workflow
execution with profile-based tool settings override. Structure tool now dynamically
applies profile configurations for LLM, embedding, vector DB, and processing parameters
based on user-defined profiles.
Key features:
Why
Solved critical workflow configuration issues:
This enables users to create profiles once and apply them consistently across
executions, improving workflow reliability and development efficiency.
How
Profile ID Propagation Chain:
API Request → Deployment Helper → Workflow Execution → File Processing → Metadata Storage
Key Implementation Points:
Files Modified:
Security: Profile ownership validation prevents unauthorized profile usage
Logging: Detailed change tracking shows exactly what overrides were applied
Compatibility: All changes optional, preserving existing workflow functionality
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.