-
Notifications
You must be signed in to change notification settings - Fork 377
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
Revise the runtime code we provide to users for configurability #2471
Comments
@benbrown added two examples of middle-wares and @luhan2017 may have more options |
#2423 this PR is to enable a telemetry middleware in botproject. |
@benbrown, are you working on this right now? @zidaneymar in my team is working on some issues relates to middleware and some specific channel configurations. He probably can resolve most of the items in this list. |
@luhan2017 I am not actively working on the code - I was just trying to gather requirements for the next revision of the code, particularly as it relates to the new "eject" feature described in #2470 |
OK, then I will ask @zidaneymar to work on this, and we can discuss more details if needed. |
This draft would bring great enhancement. |
Hello @luhan2017 ! I'm doing some refactors on bot project and integration with other potential deployment avenues such as azure Functions down the road. Do you have a branch where you folks are working? |
addressed via #2679 |
This is a draft ticket the requirements for this work are being gathered right now.
We need to make sure the runtime code we provide to users during the eject process (#2470) as well as when we deploy a bot in its unmodified form is well designed for configurability and extension.
Some major behaviors should be configuration driven:
We will need to make sure that, when deployed, the runtime will still be able to find the assets, and those assets will be in a logical location.
MORE TBD
The text was updated successfully, but these errors were encountered: