Amplify environment plugin requires restart of VSCode after pulling new environment

[abdallahshaban557]

Hi Poya,

I have noticed that after I create a new Amplify project, or pull a project using the CLI, I need to restart VSCode before the plugin starts showing my environment details.

Is this something that can be addressed?

[poyashad]

Hi @abdallahshaban557 I think this is possible by also having a filesystem watcher on the team provider file. I will have a look at it

[abdallahshaban557]

Awesome! Thank you, Poya!

[poyashad]

Hi @abdallahshaban557,

I think I have found a solution.

I looked at the activation events (specific events that activate the extension). Before this feature request, the extension activation event was an event that looked for a team-provider-info.json file in the workspace at startup. This was only triggered at startup, and if the file was not found, the extension was not activated. And if the file was added later while vs code was running, this new file was not caught by the activation event.

With this fix, the extension is activated at startup, but in a kind of silent mode with a file system watcher subscription. When the file system watcher detects the creation of the team-provider-info.json file. Then the extension is activated.

This means that when you create a new Amplify project, or pull a project using the CLI, the extension will detect the creation of the team-provider-info.json and display the extension in the status bar.

Thanks for the feature request, please let me if this fix works for you and what you think.

Best Regards!

[abdallahshaban557]

Will try this out! Thank you so much, @poyashad!

[abdallahshaban557]

I am noticing this error when I do these steps:

• I deleted my Amplify project locally using the CLI (the Amplify Environment was not removed)
• I pulled another Amplify project to my local machine
• I started seeing multiple environments from the Extension

[poyashad]

Thanks for testing it out @abdallahshaban557 !

I think the extension will have to do some checks and also watch for when the project gets deleted. And go into "silent mode" again.

I will take a look at it!

[poyashad]

Hi @abdallahshaban557,

Since the extension did not detect the deletion of the team-provider-info.json file, it could not disable/deactivate/hide the extension. I have now added a file system watcher that looks for a deletion. Could you please run some tests to see if it works as intended?

Thanks!

[abdallahshaban557]

Hi @poyashad - I have tried it again, and it seems the issue was not resolved. I am still seeing duplicate environments when I try to remove an Amplify project.

[poyashad]

Hi @abdallahshaban557, i will take a look and try to duplicate the issue!

[poyashad]

Hi @abdallahshaban557 Sorry for the inactivity! Could you please just post the AWS Amplify CLI commands that are triggering this issue? I will try to replicate the problem.

[abdallahshaban557]

Hi @poyashad - The command I was using is amplify pull

[poyashad]

Thanks @abdallahshaban557 i will try to replicate and debug.