AppSync configuration removed from AWS-Exports during env init, checkout

[sean-cedar]

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

v14.21.2

Amplify CLI Version

11.0.5

What operating system are you using?

Debian

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No

Describe the bug

When changing Amplif environments via the cli using "amplify init", the aws-exports.js file is updated, removing any existing appsync config that has already been deployed to the environment.

Expected behavior

The aws-exports.js file should be refreshed with the appsync configuration that has been deployed to the environment.

Reproduction steps

1. Run amplify init
2. Select existing environment
3. Review aws-exports.js

Project Identifier

No response

Log output

# Put your logs below this line

Additional information

No response

Before submitting, please confirm:

• 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.

[josefaidt]

Hey @sean-cedar 👋 thanks for raising this! Are you still experiencing this issue? Are you able to checkout other environments with amplify env checkout <env-name>?

[sean-cedar]

Hi @josefaidt - the AppSync configuration is removed from AWS-Exports when using the amplify env checkout <env-name> command. When environments are initialized using amplify init or amplify env checkout, I must then remove codegen using amplify remove codegen and then add back the API using amplify add codegen --apiId <apiId>.

[josefaidt]

Hey @sean-cedar thanks for clarifying! I'm able to reproduce this using the following steps:

1. amplify init -y
2. amplify add codegen --apiId <some-api-id>
3. observe AppSync details are available in src/aws-exports.js
4. amplify env add next
5. observe AppSync details have been removed from src/aws-exports.js

Marking as a bug and transferring to the API repo for tracking purposes