Problem
After ddev push pressable the provider prints nothing about what the import changed on the remote beyond the URL rewrite and cache flush. On a recent push to a Pressable staging site we had to run the checks by hand to learn that the platform's Jetpack connection was gone, two platform plugins had been deactivated, the admin user had been replaced, and the environment type was what we expected. #5 adds a target line before the push; this is the matching report after it.
Proposed change
At the end of db_push_command, print a short report captured over the same SSH session:
wp plugin list --status=active --field=name # diff against the pre-push list
wp eval 'echo wp_get_environment_type();'
wp eval 'echo Automattic\Jetpack\Connection\Manager::is_connected() ? "connected" : "disconnected";' # only if Jetpack is active
wp user list --field=user_login --role=administrator
wp db tables --all-tables | wc -l
Something like:
push: done -> https://<site> (WP_ENVIRONMENT_TYPE: staging)
active plugins: +<client-plugin> +<other-plugin> -jetpack -automattic-for-agencies-client
jetpack: inactive
administrators: 2 (was 3)
tables: 59
The plugin diff and the administrator count are the two lines that would have flagged the platform-state loss immediately. If the provider grows the preservation logic proposed in the companion issue, this report is where it says what it restored.
Notes
Problem
After
ddev push pressablethe provider prints nothing about what the import changed on the remote beyond the URL rewrite and cache flush. On a recent push to a Pressable staging site we had to run the checks by hand to learn that the platform's Jetpack connection was gone, two platform plugins had been deactivated, the admin user had been replaced, and the environment type was what we expected. #5 adds a target line before the push; this is the matching report after it.Proposed change
At the end of
db_push_command, print a short report captured over the same SSH session:Something like:
The plugin diff and the administrator count are the two lines that would have flagged the platform-state loss immediately. If the provider grows the preservation logic proposed in the companion issue, this report is where it says what it restored.
Notes
mainplus fix: run WP-CLI against the docroot and keep PHP notices out of captured values #4 and feat: print the push target and refuse production environments #5 applied.