wp-cli VS wp-migrations

As of my last knowledge update in January 2022, the list of WordPress CLI commands may have expanded or changed. It's always a good idea to check the official WP-CLI documentation for the most up-to-date information. Here's a list of common WP-CLI commands as of my last update:

Is a Docker WordPress Environment focused on the development of WordPress plugins and themes, supports WP-CLI, phpMyAdmin, Xdebug and WordPress Coding Standards - WPCS.

If you’re handy with scripting, check out WP CLI https://wp-cli.org - that’s probably what you’re after.

Another solution (if you are a bit techy) could be to use WP CLI and to a search/replace in the database.

I have played around with implementing some CI/CD pipelines for wordpress, specifically a managed wordpress instance, and I've found some things that work. At the core of it all has been WP-CLI backed by ansible.

/s. Really though I've never had to do much database cleaning, and in the event I do need to interact with the database, I prefer to use the wp-cli tool.

But when installed directly via composer you end up using this script as the entry point: https://github.com/wp-cli/wp-cli/blob/7c5999512131c8e6b63d1200dedd53984078ce2c/bin/wp

1) Build your own in PHP using something like https://github.com/cuisine-wp/wp-table-migrations or https://github.com/deliciousbrains/wp-migrations - it needs to be done specific to your database structure, thats why you don't see off the shelf options.