Disabling cloud-api does not delete/remove the stack

[aws-amplify]

Disabling cloud-api does not delete/remove the stack

[UnleashedMind]

The awsmobile-cli uses the mobile hub api to perform its operations in the cloud.
Your backend mobile hub project might have more contents than the cloud-api alone, so disabling the cloud-api feature does NOT mean the whole mobile hub project is deleted. It only removes that feature from the backend mobile hub project.
You can execute awsmobile delete to delete the whole backend mobile hub project. It is still recommended that you check and make sure all the aws resources in the mobile hub project are removed by the mobile hub.

[jbarwick]

I didn't say delete the whole project. I said delete the CloudFormation stack. Which is the cloudAPI stack. I should have made that clear when I said, "backend"

[jbarwick]

Also, when deleteing the stack, the lambda functions are not deleted. Have to go delete those manually.

Again, if I say "awsmobile cloud-api disable" I expect to see the operation DELETE_STACK, not UPDATE_STACK

Stack is the CloudFormation Stack...APIGateway/lambda...NOT the whole project.

[jordanranz]

It is possible to delete a cloud formation stack after migrating to use the new Amplify CLI. I will go ahead and move this to the amplify-cli repo to further comment.

[UnleashedMind]

@jbarwick
What you found is correct.
But the mobile hub project has been deprecated, there's no active development on it at this moment.

[UnleashedMind]

close the issue for now, feel free to reopen if needed.

[github-actions]

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.