We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm unable to connect to a remote Pantheon site to run Drupal Console commands.
Locally, I've setup a file called ssh.yml in console/sites that has the following parameters (certain identifiable items have been replaced be #####:
dev: root: /srv/bindings/#####/code/web host: appserver.dev.#####.drush.in user: dev.##### type: ssh port: 2222 extra-options: '-o "AddressFamily inet"'
When I run this command: drupal @ssh.dev
drupal @ssh.dev
I get this output: PTY allocation request failed on channel 0
PTY allocation request failed on channel 0
I can run Drush commands against this and other Pantheon sites without a problem.
Is my ssh.yml file setup correctly for Pantheon or is there something else going on?
Details:
Any help is greatly appreciated. Thanks!
The text was updated successfully, but these errors were encountered:
Thanks for the report @ryanprager, was fixed on hechoendrupal/drupal-console-core#349 and will be included in release 1.9.0
Sorry, something went wrong.
No branches or pull requests
Problem/Motivation
I'm unable to connect to a remote Pantheon site to run Drupal Console commands.
How to reproduce
Locally, I've setup a file called ssh.yml in console/sites that has the following parameters (certain identifiable items have been replaced be #####:
When I run this command:
drupal @ssh.dev
I get this output:
PTY allocation request failed on channel 0
I can run Drush commands against this and other Pantheon sites without a problem.
Is my ssh.yml file setup correctly for Pantheon or is there something else going on?
Details:
Any help is greatly appreciated. Thanks!
The text was updated successfully, but these errors were encountered: