- Notifications
You must be signed in to change notification settings - Fork 426
feat(command-env): add migrate subcommand #3876
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
Conversation
da4bae9
to 62718d5
Compare There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ashalfarhan, sorry for the very later review.
I changed the command a bit to use options instead of arguments.
It makes the purpose of each site id more explicit.
I also added error handling to handle when the CLI can't get the site from the id.
Finally, I think transfer
can be confusing for this command, as it doesn't remove the variables from the from
site (I should have figured this out sooner).
We could try calling it env:migrate
or env:clone
, what do you think?
Yeah, I think it's better to use options instead of arguments. Btw |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎸
🎉 Thanks for submitting a pull request! 🎉
Summary
Fixes #3575
This PR will add the ability to transfer environment variables from one site to another.
If you want to send env vars from one site to another you can run this subcommand.
Given 2 arguments, the basic usage is:
siteIdA
, then it will exit because nothing to transferSo users can use this command without opening their browser to copy and paste the env vars from one to another.
Notes:
For us to review and ship your PR efficiently, please perform the following steps:
passes our tests.
A picture of a cute animal (not mandatory, but encouraged)