Great article, you concisely explained the exact reason why we have always avoided the workflow Amplify advocates under their Team environments page.
We've instead kept the concerns of Amplify environments and git code branches separate to avoid running into the issues you outline. We haven't unfortunately solved the CI/CD dance yet as each developer manages their own Amplify backend, but we've at least avoided the issues you outline above.
I'm not sure why the categories data in team-provider-info.json needs to be stored separately per environment under source control. There must be a good reason, but seems like there's a better way to avoid all this pain.
For the past 15 years, I had the opportunity to work in various types of projects, in a number of industries. In that time I have developed some thoughts about software and the process of creating it.
Great article, you concisely explained the exact reason why we have always avoided the workflow Amplify advocates under their Team environments page.
We've instead kept the concerns of Amplify environments and git code branches separate to avoid running into the issues you outline. We haven't unfortunately solved the CI/CD dance yet as each developer manages their own Amplify backend, but we've at least avoided the issues you outline above.
I'm not sure why the
categoriesdata inteam-provider-info.jsonneeds to be stored separately per environment under source control. There must be a good reason, but seems like there's a better way to avoid all this pain.Hi Dan,
First, thanks for the feedback.
We also just can't figure out why the
team-provider-info.jsonworks like that. It'll be interesting to hear the actual reasons.Can you further explain your workflow? Each dev works on their own environment, but how do you merge changes into the main environment?