aws-amplify / aws-amplify/amplify-cli

Amplify-cli@env renaming an environment

Open
#685 29 comments 9 reactions 0 assignees View on GitHub
feature-request multienv p3
Dominant language
TypeScript
Stars
2.9k
Forks
825
Avg merge
11d 23h
Merged PRs (30d)
2

Description

**Is 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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.