-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
drush status fields have changed #3076
Comments
Major releases may introduce changes to clean things up or make things more clear. Scripts should not be parsing table output. Instead, use That said, we could potentially convert from "DB" back to "Database". The shorter names are a little better for table output, though, as the right column can often contain long strings, so there is a benefit to shortening the left column, as that will tend to reduce wrapping in the long term. |
Note also that Drush 9.0.0-beta5 abandons the old Drush command processor, and replaces it with the Symfony Console runtime. Drush 9.0.0-beta4 and earlier are strongly deprecated; there is no need to use those versions when comparing behavior change in Drush. Just compare 9.0.0-beta5 and later with versions of Drush 8. |
Correct - please use yaml or json formats for scripts. |
Drush 9 has introduced a change to the output of
status
somewhere along the line:Drush 8 and Drush 9-alpha1:
Drush9-beta7:
This change from "Database" to "DB" has clobbered our build scripts as we're parsing information from this output. I'm curious if this change is necessary/intentional?
The text was updated successfully, but these errors were encountered: