configured env disappeared from amplify env list, resources still running

Describe the bug I configured 2 environments for a project I’m building. Dev and Master using the same patterns described in the multi-env doc page. I have not done anything with the master environment for a couple of weeks and now it is no longer showing up when I type amplify env list. amplify env get --name master returns No environment found with the corresponding name provided

To Reproduce I’ve not reproduced this since but here’s what happened Steps to reproduce the behavior:

1. Use amplify env add to add a new environment
2. Switch development back to a different environment
3. Wait for days (personal theory is that this is related to the timeout of API Keys like described in #980 but I’m not certain
4. run amplify env list

Expected behavior I’d expect to see both the dev and the new env I created in the list

Observed Behavior

$ amplify env get --name master
No environment found with the corresponding name provided

All of the resources for that environment are still running - S3 buckets, API and Elasticsearch instances. I just can’t control them anymore.

Desktop (please complete the following information):

• OS: MacOS 10.14.3

• Browser n/a

• Amplify version 1.1.7 - may be worth noting that `amplify env add was run in 1.1.0

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context Add any other context about the problem here.

[kaustavghosh06]

@poppybank If you didn’t check in your team-provider-info.json file in a VCS before you lost the reference to it, you could retrieve the “awscloudformation” information from the that environments corresponding to that environment from the parent Cloudformation stack (in the Outputs section) in the AWS Cloudformation console.

You can copy-paste this info in the amplify/team-provider-info.json file (use your other enviornment as a reference) and then “amplify init” the project and select the environment that you just added to initialize and use the environment you just added to your team-provider-info.json file.

[ezagala]

amplify pull --appId [APP_ID_HERE] --envName [ENV_NAME_HERE] did the trick for me.