Open SeanBannister opened 6 years ago
Thanks for the feedbacks @SeanBannister. We are aware of that issue, and we have notified our mobile hub team about it, will notify you when there is any update. You suggestion about the extra parameter in the cli will also be considered.
agreed. it looks like appsync is the only resource that gets removed and everything else is left orphaned.
Related to this discussion: CloudFormation can be used to build / tear down resources, as long as MobileHub is not used.
When a user runs
awsmobile delete
a number of resources aren't deleted and are left orphaned in the account. Could I suggest that these are documented somewhere so the user knows what to delete manually. It appears to be dynamodb and s3, are there any other resources I should be aware of?An alternative could be providing an extra parameter on the
awsmobile delete
command that also deletes these resources. This is handy in development when spinning up multiple environments and you don't care about the data.