Can not create new environment when adding New App (Host Web App)

[bergmorten]

Before opening, please confirm:

• I have checked to see if my question is addressed in the FAQ.
• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

App Id

d34x9npy2tqygn

AWS Region

ca-central-1

Amplify Hosting feature

Backend environments

Frontend framework

Vue

Next.js version

Does not use Next

Next.js router

N/A

Describe the bug

I want to add a App and create a new backend environment which are not shared with other apps connected to the same branch.

In build settings I select create new environment and fill in name wcscanada both for app name and environment. Do not know why the pull down of App name does not reflect the app-name given (possible another bug).

Summary seems ok:

But the when I deploy it try to create an environment with the same name as the branch name (template).

One of the errors:

I my setup this does not work since I need to have separate environment per app.

Need also help to clean this up.

I tried first to deploy this app in another region where I also another app with this backend environment. However if I try to delete this app it will also delete the environment of the existing app. How do I delete an app and keep the environment?
See app id d38c3xshp5shlw and d3h2imtpur0g0t in region us-east-1

Expected behavior

Create app easy with separate environment so that database, Cognito and roles are unique.

Reproduction steps

1. Create new app - web hosted
2. Connect to git hub and a branch
3. Under build setting set Create new environment with a name other than the branch name
4. Should create this environment, but is does not. It use the branch name

Build Settings

No response

Log output

# Put your logs below this line

Additional information

No response

[Jay2113]

Hi @bergmorten 👋 , thanks for raising this and for providing detailed reproduction steps.

The behavior outlined in this issue seems related to #3745. Please refer to my comment here: #3745 (comment) which outlines a workaround to use the USER_BRANCH environment variable.

Closing this to keep all the communication in the same place. Please track #3745 for any further updates.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

[github-actions]

This issue has been automatically locked.