feat(nodes): add managed file inputs#9302
Conversation
|
@Gohankaiju I'm afraid there are merge conflicts in api_app.py and invocation_services.py. After you resolve these, please |
|
@lstein Thanks for the heads-up! I've merged |
|
@Gohankaiju It looks like a CI action is failing for docs. To fix: Then add, commit, and push |
Add FilesInterface to the generated invocation context docs and pick up the new max_file_upload_size_bytes setting. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
@JPPhoto |
Summary
Closes #9300
This PR adds a first pass of managed file inputs for custom nodes.
It introduces a lightweight
FileFieldflow so node authors can accept document/data files through the InvokeAI UI, instead of requiring users to provide server-local paths or embedding file contents in workflow data. This is especially important for hosted deployments, but is also useful for local/self-hosted users because files can be attached directly from the node input UI.What is included:
FileFieldinvocation field supportfile_idreferencescontext.filesThis first pass is intentionally scoped to node inputs. It does not add gallery/boards integration, previews, thumbnails, search, starring, or bulk file management.
Clearing a node input currently removes the node's reference only. Automatic server-side deletion is left out for now because the same
file_idmay still be referenced by saved workflows, copied nodes, or queued executions.Related Issues / Discussions
Refs #9300
QA Instructions
Automated checks run locally:
Startup smoke test:
Confirmed startup reached
Invoke running on http://127.0.0.1:9090.Still validating before marking ready for review:
FileFieldcontext.filesMerge Plan
Draft PR for design and implementation feedback.
No database schema migration is included. No gallery/boards file lifecycle is introduced in this first pass.
Checklist
What's Newcopy (if doing a release after this PR)