Skip to content
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

Add use command to setup configuration for the user #74

Open
happyRip opened this issue May 3, 2023 · 1 comment
Open

Add use command to setup configuration for the user #74

happyRip opened this issue May 3, 2023 · 1 comment
Assignees
Milestone

Comments

@happyRip
Copy link
Member

happyRip commented May 3, 2023

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'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?

Yes.

cc @adriansmares @johanstokking

@happyRip happyRip added this to the 2023 Q2 milestone May 3, 2023
@happyRip happyRip self-assigned this May 3, 2023
@github-actions github-actions bot added the needs/triage We still need to triage this label May 3, 2023
@adriansmares
Copy link
Contributor

adriansmares commented May 3, 2023

In ttn-lw-cli we have a configuration file .ttn-lw-cli.yml which is created/edited by the use command. The file itself is processed using viper.

Since we already use pflag, I think tying everything together with viper shouldn't be too bad, but this needs some digging.

@NicolasMrad NicolasMrad removed the needs/triage We still need to triage this label May 9, 2023
@adriansmares adriansmares modified the milestones: 2023 Q2, 2023 Q3 May 23, 2023
@KrishnaIyer KrishnaIyer modified the milestones: Q3 2023, Backlog Sep 27, 2023
@KrishnaIyer KrishnaIyer assigned KrishnaIyer and unassigned happyRip Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants