Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Amplify-cli@env renaming an environment
See original GitHub issueIs your feature request related to a problem? Please describe.
Is it possible to rename an environment from, say “maaster” to “master”? The issue I’m currently facing is that I did not rename the environment when I switched to amplify-cli@env (so my only environment is called: “NONE”). I would like to rename this NONE environment to dev while preserving existing backend resources.
Describe the solution you’d like
amplify env rename dev
> Enter new name: (dev)
Describe alternatives you’ve considered Creating a new branch, although I have some data, currently, that I’d rather not lose.
Additional context amplify-ci@env --version: 0.2.1-multienv.22
Issue Analytics
- State:
- Created 5 years ago
- Reactions:5
- Comments:17 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@kaustavghosh06 Hey is there any update on if/when this might be prioritised? I very foolishly named the env we now use in production as test and it would be great to either rename this or somehow switch the branch we use for production to be a new branch which has the correct name
@ajhool Let’s keep this open since this is a useful feature request (although it won’t be immediately prioritized).