Closed (fixed)
Project:
Configuration Update Manager
Version:
2.0.x-dev
Component:
Base module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
23 Mar 2019 at 17:31 UTC
Updated:
5 Jun 2022 at 00:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
jhodgdonThat first deprecation message is not really valid. Seems to be a problem with the static analysis. It's coming from this code:
So, I think we can ignore this.
The second deprecation message about the Drush logger is somewhat valid.
http://www.drush.org/api/master/Drush/Drush.html#method_logger
says:
So, apparently we should be injecting the logger service into our Drush commands service, apparently... though I am not sure if we can do that easily. I don't know if the Drupal services file will inject Drush services? Probably not. So I am inclined to leave this. We need the logger service for interoperability -- to support both Drush 8 and Drush 9. I think we can afford to leave that deprecated code around until we no longer want to support Drush 8... which is I think around the time that Drupal 7 goes away.
When that happens, our Drush code should be refactored so that it no longer attempts to support Drush 8, and no longer calls Drush::logger().
So, I am retitling this issue and postponing it.
Comment #3
jhodgdonDrush 8 doesn't work with Drupal 8 any more at all. We should just stop supporting it, and move to Drush 9. So, un-postponing this.
Comment #4
samaphpThank you all for the efforts, Can you please help to write some details about what we can do to help in this issue?
Many thanks!
Comment #5
jhodgdonYes, what needs to be done is to remove the code in this module that supports Drush 8, and leave in the code that supports Drush 9.
Comment #6
samaphpPerfect, thank you for the clarification.
Comment #7
jhodgdonHere's a patch, which I haven't tested. I am not sure if we can create an automated test for the Drush commands... it might not run in the Drupal testing infrastructure, not sure -- it would need Drush to be present, so I guess we'd need to add that to the composer.json for testing only.
So at least this should be tested manually -- we need to see if all of the Drush 9 commands still work.
Comment #8
jhodgdonOK, the main tests passed. Minor coding standards fix.
Comment #9
bserem commentedI just want to mention that Aegir servers still depend on Drush 8, so it might be a good idea to postpone this.
Comment #10
jhodgdonBut Drush 8 does not work with Drupal 8, as far as I know... right?
Comment #11
jhodgdonSee http://docs.drush.org/en/master/install/ for compatibility list. Drush 8 no longer works for Drupal 8.4.x and later. As such, this module should not support Drush 8 any more.
Comment #12
bserem commentedAegir and BOA (also an Aegir stack) do not support Drush 9 yet. I do not know the internals of these systems, but they succesfuly use Drush 8 on Drupal 8 and I can assure you that if drush 9/10 is installed through composer things fall apart.
There is a lengthy discussion here: https://www.drupal.org/project/provision/issues/2953349
If you release a -dev version without drush 8 support I can try it on an Aegir system and see how it goes.
Comment #13
jhodgdonThat's odd, because the Drush project's web site definitely says Drush 8 does not work for Drupal versions after 8.4. I thought I had experienced that myself... is Aegir using a modified version of Drush 8 that does continue to work for later Drupal versions?
Comment #14
bserem commentedBOA uses 8.3.2-dev which is compiled upon installation of the Aegir stack from source.
8.3.2 was released on November 2019.
Version 8 is active on github (I wasn't aware of this either): https://github.com/drush-ops/drush/commits/8.x
I can guarantee you that I am running a lot of cim/cex/updb/uli/migrate*/sapi* commands from drush 8 to drupal 8.8+ on Aegir without issues, while at the same time use drush 10 locally. Config_update and config_devel are no exception.
Comment #15
jhodgdonOK, well the Drush maintainers need to update their web site then.
Comment #16
jhodgdonI guess if Drush 8 is still supported and still works with Drupal 8/9, we should also postpone this issue. Thanks for bringing up the objection @bserem!
Comment #17
pasquallereroll
Comment #18
pasqualleComment #20
pasqualleComment #22
pasqualle