Running Copilot init second time gives error

[sundarnarasiman]

This is during the scenario of running Copilot init command. We can run 'copilot init' command on a completely developed co-pilot application, like the voting app below.

Voting app

https://github.com/copilot-example-voting-app/vote
https://github.com/copilot-example-voting-app/results
https://github.com/copilot-example-voting-app/api

If we run the 'copilot init' second time it fails, after successful first ‘copilot init’ execution on the same AWS account number for that application. The second attempt can be on same desktop environment or different desktop environment. Basically it's checking for existence of certain IAM roles. If it already exists, copilot thinks that the app is previously setup and it fails. This needs to be fixed. This is a valid use case. Because a development team can have a single Copilot/ECS application, which needs to be set up by multiple developers in their own desktop environment (MacOS/Linux/Win10).

[efekarakus]

Heya @sundarnarasiman what's the error message that you see?

[efekarakus]

Closing due to lack of response please feel free to re-open!