@yehudah,
Unfortunately, I cannot. It’s an internal-only site. I know that probably makes things more cumbersome, but hopefully I can provide any information needed to figure things out.
Thanks!!
I was able to determine, using ‘wp –debug <subcommand>’ that the issue seemed to be that I wasn’t able to connect to the database. This is running in AWS’s Elastic Beanstalk and somehow a security group was changed and no loner allowed tcp 3306 to the database from where I was running the commands.
