You need to disable a module on a Magento Commerce 2 3 Cloud project and remove its database tables The module uses the declarative schema system to manage its database changes
Deleting the module from the git repository and leaving the record in config.php? That's a recipe for disaster! You'd end up with a mismatch between the code and the configuration, which could lead to all sorts of problems.
Disabling the module directly on the production environment? That's a bold move! I'd be worried about any potential data loss or compatibility issues. Better to test it out on the local environment first.
Disabling the module on the local environment and committing the config.php file sounds like the right approach. That way, the change is deployed to the production environment without any database issues.
Juan
4 hours agoArlie
6 days agoEdda
18 days agoKimberlie
3 days agoAllene
19 days agoAnthony
22 days agoVerlene
25 days ago