Open hanna-becker opened 1 year ago
Hi @hanna-becker 👋 , thanks for raising this and for sharing detailed information about your use case.
Unfortunately, we do not support the workflow of converting an existing git based CI/CD Amplify app to a manually deployed Amplify app.
The only workaround in this case would be to create a new Amplify app for your frontend to perform manual deployments and then maybe you can consider sharing your backend across apps: https://docs.aws.amazon.com/amplify/latest/userguide/reuse-backends.html
Hi @Jay2113, thank you for the suggested workaround and the link. We will investigate this option.
So is it correct that there is currently no way to completely disconnect a repository from an Amplify app once it has been connected through the console? I think there should have been clear communication in the form of a big red warning box in the docs that taking this step is a one-way door that cannot be undone. (There may be now, actually, I haven't checked.)
I also wonder why this gap hasn't been closed, yet, by the Amplify team. I might be mislead, but from a user's perspective it doesn't seem like it would be a terribly large development effort to implement allowing users to disconnect their repositories.
Hi @Jay2113, one question about your suggested approach: If we create a new app that reuses the existing backend, will we be able to delete the old app afterward, while keeping the original backend?
Before opening, please confirm:
App Id
d3mqvgiptwomr
AWS Region
eu-central-1
Amplify Hosting feature
Deployments, Manual deploys
Frontend framework
Angular
Next.js version
N/A
Next.js router
N/A
Describe the bug
We connected our git repo through the amplify console and set it up for automatic deployments on each commit about 1.5 years ago. Because the amplify CI/CD does not cover all of our needs, we'd now like to change to manual deployments via amplify publish and do the deployment in the pipeline of our git provider, instead.
We disconnected all the branches in the amplify console (for lack of disconnecting the entire repo) and then added hosting via the cli with "amplify add hosting":
However, when then running "amplify publish", while the backend deployment passes without any issues, for the frontend deployment we get the following error:
Expected behavior
amplify publish works and deploys the backend and frontend.
Reproduction steps
Build Settings
No response
Log output
Additional information
A similar issue was reported before and from the reactions I see there, it seems like a lot of people are confused that it was closed without a resolution: https://github.com/aws-amplify/amplify-hosting/issues/956