-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
changes in worker and tools related to sdk filestorage #844
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - @muhammad-ali-e don't you need to update the tool's requirements.txt to use the intended SDK version?
@chandrasekharan-zipstack It will be updated once we transition out of the beta phase |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look fine. Except for tool version changes suggested by @chandrasekharan-zipstack
Co-authored-by: Chandrasekharan M <[email protected]> Signed-off-by: ali <[email protected]>
Co-authored-by: Chandrasekharan M <[email protected]> Signed-off-by: ali <[email protected]>
Co-authored-by: Chandrasekharan M <[email protected]> Signed-off-by: ali <[email protected]>
|
What
Remote FileStorage
.Why
FileStorage
feature.How
hasattr(self, "workflow_filestorage")
for backward compatibility, as the upcoming SDK version will introduce theworkflow_filestorage
property in theBaseTool
class.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.