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
To simplify the migration tool setup process for the user, as some of the users have problems with setting up the environment.
What is already there? What do you see now?
We use env variables and flags to setup the environment.
What is missing? What do you want to see?
A simple to use command to setup everything for the user.
Environment
n/a
How do you propose to implement this?
Implement a use command similarly to the lw-stack's use command. The user could provide a URL to a device or app he'd like to export (or a server if he wants to export multiple devices/apps) and the environment would be set automatically.
I'm not sure if it would be easy for other sources, but should be doable for TTS.
How do you propose to test this?
Use the command to setup the migration tool for some deployments and export devices.
Can you do this yourself and submit a Pull Request?
Summary
Add
use
command #56 (comment)Why do we need this?
To simplify the migration tool setup process for the user, as some of the users have problems with setting up the environment.
What is already there? What do you see now?
We use env variables and flags to setup the environment.
What is missing? What do you want to see?
A simple to use command to setup everything for the user.
Environment
n/a
How do you propose to implement this?
Implement a use command similarly to the
lw-stack
'suse
command. The user could provide a URL to a device or app he'd like to export (or a server if he wants to export multiple devices/apps) and the environment would be set automatically.I'm not sure if it would be easy for other sources, but should be doable for TTS.
How do you propose to test this?
Use the command to setup the migration tool for some deployments and export devices.
Can you do this yourself and submit a Pull Request?
Yes.
cc @adriansmares @johanstokking
The text was updated successfully, but these errors were encountered: