Skip to content
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.

Sign up for GitHub

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

Jump to bottom

lando pull without lando init first doesnt work, lagoon #5

Open
pirog opened this issue Feb 2, 2021 · 7 comments
Open

lando pull without lando init first doesnt work, lagoon #5

pirog opened this issue Feb 2, 2021 · 7 comments
Labels
Needs Triage

Comments

@pirog
Copy link
Sponsor Member

pirog commented Feb 2, 2021

Wasn't able to replicate this but creating a placeholder in case someone else can. Original issue reported by @Schnitzel. Steps to replicate:

  1. git clone Lagoon project that has already been lando inititialized for use with lando
  2. lando pull and choose to add new key. Go through new key add workflow and continue.
  3. lando pull fails.
@mglaman
Copy link

mglaman commented Feb 13, 2021 •
edited
Loading

Is this the output? I had a local repo and ran lando init to setup the recipe. Then I ran a pull. I had added the key during the recipe init.

? Pull database from? contribkanban-master
? Pull files from? none
Refreshing aliases...


  Command la was not found. Drush was unable to query the database. As a result, many commands are unavailable. Re-run your command with --debug to see relevant log messages.

@owenbush
Copy link

@mglaman I had that error and it was because la is a lagoon specific drush command that does not exist unless you have required the amazeeio/drupal_integrations composer package. Have you added that to your composer.json?

@mglaman
Copy link

mglaman commented Feb 15, 2021

Nope! I didn't know it existed. I'll add that now and try again! Thanks, @owenbush

@mglaman
Copy link

mglaman commented Feb 15, 2021

That fixed the la error, now I get a 400 from the API. I'll debug more later

Refreshing aliases...

In RequestException.php line 113:

  Client error: `POST https://api.lagoon.amazeeio.cloud/graphql` resulted in a `400 Bad request` response:
  <html><body><h1>400 Bad request</h1>
  Your browser sent an invalid request.
  </body></html>


lagoon:aliases [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-d|--debug] [-y|--yes] [--no] [--remote-host REMOTE-HOST] [--remote-user REMOTE-USER] [-r|--root ROOT] [-l|--uri URI] [--simulate] [--pipe] [-D|--define DEFINE] [--druplicon] [--notify [NOTIFY]] [--xh-link XH-LINK] [--] <command>

@owenbush
Copy link

@mglaman I was receiving a 400 error from the API yesterday too, and didn't have time to figure out why. I wonder if the lagoon API was having a bad day.

@mglaman
Copy link

mglaman commented Feb 16, 2021

@owenbush The API was working. For me it seems the key in ~/.lando/keys was bad. I'm going to try and recreate that (in the middle of a rebuild now.)

@stale
Copy link

stale bot commented Aug 22, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions and please check out this if you are wondering why we auto close issues.

@rtfm-47 rtfm-47 transferred this issue from lando/lando Nov 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Needs Triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@pirog @mglaman @owenbush @rtfm-47