-
Notifications
You must be signed in to change notification settings - Fork 71
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
Playbook fails on drupal-console; geerlingguy has deprecated #1599
Comments
@rosiel, fix has been merged, OK to close? |
Yahoo! |
Greetings for all |
Thanks @red7-soporte ! Yes, the fix was applied to the dev branch. which we all thought was also the default branch of the islandora-playbook repo. The fact that 'main' is now the default branch may have been an accident with a large-scale script that changed our default default branch name from master to main. I think the intention is that
is supposed to work. The main branch is 'pinned to' our release, but ... it should be possible to also spin up the release, and this is a change purely to the playbook/installation instructions. I therefore think we should apply this fix to 'main' as well (as any other branches that should be live). @dannylamb @mjordan @elizoller (who posted about which branch should be default, back on Sept 1, in slack). |
Hi! |
The playbook fails.
Tracking down discussion on slack (thanks @mjordan and @elizoller !!) to why Drupal Console breaks the playbook:
Since Aug 17, https://drupalconsole.com/installer is no longer working. Issue: hechoendrupal/drupal-console#4262 Suggestion was to use Composer to require Drupal Console.
We get drupal console through Geerlingguy's role. https://github.com/geerlingguy/ansible-role-drupal-console It is deprecated as of August 20, 2020. (#2020mood)
On Aug 25, "unknownterritory" posted how to composer require drupal console via ansible. Can we do this in the playbook? hechoendrupal/drupal-console#4262 (comment)
The text was updated successfully, but these errors were encountered: