samjuk / m2-module-verbose-db-status
Adds a verbose mode to the setup:db:status command, to assist with debugging DB schema differences
SamJUK_VerboseDBStatus
This is a simple module that adds a verbose and extra verbose mode to the setup:db:status command.
Especially useful within a CI environment for identifying what schema changes are causing a database migration, which in turn prevents most typical zero downtime deployment strategies.
| Example with the verbose flag set | Example with the extra verbose flag set |
|---|---|
| [image: Example of the DB Status command with the verbose flag set] | [image: Example of the DB Status command with the extra verbose flag set] |
Installation
composer config repositories.samjuk-m2-module-verbose-db-status vcs [email protected]:SamJUK/m2-module-verbose-db-status.git
composer require samjuk/m2-module-verbose-db-status:@dev
php bin/magento module:enable SamJUK_VerboseDBStatus && php bin/magento cache:flush
Usage
Run the setup:db:status command, specifying the appropriate verbosity level
php bin/magento setup:db:status # Standard Magento Output
php bin/magento setup:db:status -v # Display before and after for modified values
php bin/magento setup:db:status -vv # Display before and after for modified values, and raw data diff
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
Requires 1
| Package | Constraint |
|---|---|
| php | >=7.3 |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge. A phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
More from samjuk
View vendorTurn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.