You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 27, 2020. It is now read-only.
As Abe designs the Conveyor Plug-in UI a new piece of functionality has come up for discussion.
Conveyor is all about making it easier to get data into Kibana and to that narrative we want to drop the user onto a page that has two massive buttons: Upload File and New Conveyor The new conveyor will send them through the traditional flow of selecting the type of conveyor they want to create and filling out the parameters.
The Upload File option is all about ease and speed. So we need to discuss the best way to accomplish that.
The big question is: What do we want to happen when the user uploads a file?
Do we create a flow?
Is that flow ephemeral?
Should the user have to name it?
Do we send that file data through a generic file upload flow that is pre-loaded?
If we do this how does the user delete the data?
How do we manage mappings?
More discussion to come.
The text was updated successfully, but these errors were encountered:
As Abe designs the Conveyor Plug-in UI a new piece of functionality has come up for discussion.
Conveyor is all about making it easier to get data into Kibana and to that narrative we want to drop the user onto a page that has two massive buttons:
Upload File
andNew Conveyor
The new conveyor will send them through the traditional flow of selecting the type of conveyor they want to create and filling out the parameters.The
Upload File
option is all about ease and speed. So we need to discuss the best way to accomplish that.The big question is: What do we want to happen when the user uploads a file?
More discussion to come.
The text was updated successfully, but these errors were encountered: