Skip to main content

Verification Commands

Verification commands help validate and verify the integrity of your database operations and configurations. These commands are free and do not require a commercial license.

verify​

Verify command steps and validate operations.

Alias: -vf
License: Free

Usage:

dbm verify
# or
dbm -vf

Description: Performs comprehensive verification of your Dubnium configuration, database connections, migration scripts, and environment setup. This command helps identify potential issues before running critical operations.

Prerequisites:

  • Valid dubnium.yml configuration file

Verification Checks:

Configuration Validation​

  • Validates dubnium.yml syntax and structure
  • Checks required configuration sections
  • Verifies file paths exist and are accessible
  • Validates database connection string format

Database Connectivity​

  • Tests connection to DatabaseOne
  • Tests connection to DatabaseTwo (if configured)
  • Verifies database permissions
  • Checks for required Dubnium system tables

Migration Scripts​

  • Validates migration script naming conventions
  • Checks for script sequence gaps or duplicates
  • Verifies script file accessibility
  • Validates SQL syntax (basic checks)

Environment Setup​

  • Confirms Dubnium system tables are properly initialized
  • Validates temporary path accessibility
  • Checks write permissions for output directories

Example Output:

Executing command: Verify
✓ Configuration file validation passed
✓ Database connections verified
✓ Migration scripts validation passed
✓ Environment setup confirmed
✓ All verification checks completed successfully

Common Issues Detected:

  • Missing Configuration: Required sections not found in dubnium.yml
  • Connection Failures: Database server not accessible or credentials invalid
  • Permission Issues: Insufficient database or file system permissions
  • Script Naming: Migration scripts not following proper naming conventions
  • Sequence Issues: Gaps or duplicates in migration script sequence numbers

Exit Codes:

  • 0: All verifications passed
  • 1: One or more verification checks failed

Best Practices:

  • Run dbm verify before important operations like build or deploy
  • Include verification in your CI/CD pipeline to catch issues early
  • Use in combination with dbm test for comprehensive environment validation