This repository was archived by the owner on Jul 9, 2025. It is now read-only.
Extensions - Storage: Clarifying objective #9121
Unanswered
zach-snell
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi All!
So I am attempting to evaluate a variety of aspects of Composer. In doing so, I started digging into Extensions and the MongoDB Storage extension specifically.
I wanted to clarify if the storage extension is intended to allow the bot's project files to be created / edited on a remote storage location. When the extension is enabled - all read/writes for creating / viewing a bot in composer are routed to the extension.
However, there are quite a few calls into fs which check/edit the local file system regardless of the storage override.
I wanted to clarify my understanding so I could properly define where the bug(s) exist today.
Either, storage should not blanket override all project file read/write or fs should not be leveraged in the way it is for checking / creating default file paths etc.
Beta Was this translation helpful? Give feedback.
All reactions