* Which Category is your question related to? *
Core
* What AWS Services are you utilizing? *
API (AppSync), Storage, Auth
* Provide additional details e.g. code snippets *
I'm using the new multienv package but I believe this issue is unrelated
Also, I understand why aws-exports might belong in .gitignore, but this complicated CI/CD... is there a simple CI/CD strategy for grabbing aws-exports?
There's a team provider info file that's not in the gitignore, and that file contains the environments.
After you cloned your repo to another computer, run amplify init, you will be prompted to select an environment, just select the existing environment, then the information of the aws cloud resources will be retrieved and the aws-exports.js file will be generated.
Most helpful comment
There's a team provider info file that's not in the gitignore, and that file contains the environments.
After you cloned your repo to another computer, run
amplify init, you will be prompted to select an environment, just select the existing environment, then the information of the aws cloud resources will be retrieved and the aws-exports.js file will be generated.