aws-amplify / aws-amplify/amplify-cli

Merge conflicts with multi-env with "amplify checkout env xxx"

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

Description

### Amplify CLI Version

12.10.1

### Question

There is a file `cli-input.json` that contains oAuthMetadata, with CallbackURLs and LogoutURLs props

Those properties are different for each environment. Which is causing conflict when switching "env" branches and merging changes between them.

Is there a way to avoid constant merge conflicts?

The workaround I'm using is to keep separate config files, `cli-inputs-dev.json` and copy them over when applying changes. Not very convenient.

Thanks!

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.