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 command to switch between development and production environment. #206

Open
euledge opened this issue Dec 8, 2023 · 1 comment
Open

Comments

@euledge
Copy link

euledge commented Dec 8, 2023

For use cases where different Google cloud and firebase projects are created and deployed in production and staging environments, skeet can use the skeet init --login command to switch between them, but it is not possible to easily switch between them because each execution of this command will cause authentication to firebase. However, each time this command is executed, the user must authenticate to firebase, which makes it difficult to switch easily.

It would be useful to have a command to switch between these two definitions together in the skeet CLI.

Related Resources

@euledge
Copy link
Author

euledge commented Dec 8, 2023

Usage image after implementation

Skeet Profile Command manage develop environment profiles.

$ skeet help profile 
Usage: skeet profile [command]

Skeet Profile Command to add new profile or switch profile.

Command:
  add <profile name>   add  new profile
  use <profile name>   switch profile

Add Profile

Run the following command to add a profile for Google Cloud Project and Firebase Project.

$ skeet profile add
Usage: skeet profile add <profileName>

Arguments:
  profileName  Profile Name - e.g. dev

new profile will be created.

Use Profile

If you want to switch a profile to Google Cloud Project and Firebase Project,
run the following command.

$ skeet profile use 
Usage: skeet profile use <profileName>

Arguments:
  profileName  Profile Name - e.g. dev

@euledge euledge mentioned this issue Jan 5, 2024
2 tasks
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

Successfully merging a pull request may close this issue.

1 participant