Add safeguards for pushing to Production environments - disable, set another default, confirmation?

Please add some options to:

  • Disable pushing to certain environments.
  • Allow setting of a default environment besides Production.
  • Require confirmation to push to Production.

I’ve always found the lack of safeguards for pushing in local to be concerning.

I’m working on a project pushing to a Dev environment on WP Engine. I had a failed database push (no error messaging other than “uh oh, it failed”), and had to redo it twice to succeed. This is on a minimal, nearly blank site as far as WP content goes; just some menu items.

One of those redo attempts, the dev database overwrote the production database, causing the site to go down. I’m 99% sure I checked every time to make sure I was pushing to the dev environment. Did an error happen on the backend out of my control? Did local not update the environment selector with the failed attempt when I redid a push? Did I make the mistake? (if so, it shouldn’t be so easy to make - I will never push this site to production with local, so please let me disable the option).

Thanks!

Thank you for the feature request @KMcCormack!