With a make file workflow such as drush-deploy, there may be times when a module is removed from the make file. When the code from that make file is deployed, the site can no longer find the removed module. It's in the db, but not in the code. @medlefsen has more detailed thoughts on this situation.
Is this something we can actually solve in drush-deploy or does drupal core need to fix the situation?
Are there ways we can detect removed modules and disable/uninstall on the current site prior to deploying to the new code?
What happens on rollback if we already uninstalled the module?
With a make file workflow such as drush-deploy, there may be times when a module is removed from the make file. When the code from that make file is deployed, the site can no longer find the removed module. It's in the db, but not in the code. @medlefsen has more detailed thoughts on this situation.