Amplify-cli: amplify env checkout <env> should update aws-exports.js file

[aprilmintacpineda]

Describe the bug

When you do amplify env checkout <env> the aws-exports.js file does not update, it will still contain settings of the previous environment.

To work around this, you can do amplify init and choose an existing environment and choose the you checkout to.

To Reproduce

1. Check aws-exports.js
2. Do amplify env checkout <env>
3. Check aws-exports.js
4. Realize that it hasn't changed to reflect the environment settings you are in.

Expected behavior

amplify env checkout <env> should update aws-exports.js file to reflect the settings of the current environment you checkout to.

Additional context

To work around this, you can do amplify init and choose an existing environment and choose the <env> you checkout to.

[attilah]

@aprilmintacpineda it seems to be a valid request, I marked it as a bug, thanks for reporting it.

[kaustavghosh06]

@aprilmintacpineda This should be fixed in the latest version of the CLI. Please report back if you're still seeing this issue.

[superunrelated]

Still not solved as of amplify -v 4.12.0

[bwalsh]

Still not solved amplify -v 4.18.1
Disappointing.