Added tools and tool_resources to Assistant and ThreadRequest structures #764
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.
Assistants have changed in V2 version need to adjust accordingly. Link for docs is below
We are migrating assistants from v1 to v2 and have files associated with them. When we switched OpenAI was returning error saying there are no files associated with the assistant. V2 version takes to files little differently
A similar PR may already be submitted!
Please search among the Pull request before creating one.
I did not find any existing PR for this
Describe the change
The change add Tools and ToolResources to ThreadRequest structure and ToolResources to Assistant structure. With this when you retrieve assistant you get tool resource and you can pass that along when you create a thread. Without this you can not create threads and OpenAI returns error saying tool_resources.code_interpreter.file_ids is required
Provide OpenAI documentation link
https://platform.openai.com/docs/assistants/migration
Describe your solution
Solution is simple to update the response definitions for v2 version of the assistant. .
Tests
Did not add any tests. Ran current tests and they seem to be working fine
Additional context
Here is how we use it.
Issue: #XXXX