View in #community on Slack
@ivanchaquea: Hello, I have a question about drush and pantheon aliases. 99% Of the time I have no issues with that workflow, even using windows 10. I just use lando to set that up and works great.
Now I have a site that needs to be built using drupal 9, i cannot use the pantheon drupal now dev organization, what i did was to install a drupal 8 site and update it to drupal 9 with composer
I set up my local drush alias under ‘drush/sites’
and now lando and local drush run into this error when I try to use alias to clear cache in dev for example
@ivanchaquea:
Exit Code: 126(Invoked command cannot execute)
Working directory:
Output:
================
Error Output:
================
sh: /code/vendor/drush/drush/drush: Permission denied
@ivanchaquea: Is this something that is expected to happen when updating a d8 pantheon site to d9?
@sparklingrobots_(admin): @ivanchaquea I’m not sure about this specific error. The only way to get the correct DB version for D9 is via the specific path here: https://pantheon.io/docs/drupal-9#create-a-new-drupal-9-site-with-integrated-composer
Pantheon Docs: Drupal 9
So it’s possible that your error is coming from not having that db version or some other small detail about that process.
@sarahg: Might need to adjust permissions on the Drush executable, like this https://pantheon.io/docs/drush-versions#site-local-drush-usage
Pantheon Docs: Managing Drush Versions on Pantheon
@ivanchaquea: @sparklingrobots_(admin) Thank you, that was the answer, it does let me run drush when I use that custom upstream vs updating the site from d8 to d9, And thank you @sarahg, Tried to change the permissions inside lando but seems like the issue with the permissions with alias happens in the remote server, but its because it doesnt point to the right place due to how I did this update
@sparklingrobots_(admin): @ivanchaquea thanks for the update! it’s good to know so that we can share it with other folks too 