-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
lando acli pull:db not working as expected #27
Comments
I experienced this issue after ACLI updated to any version newer than I use the "drupal9" and "drupal10" recipes rather than the "acquia" recipe. Here's a tooling command that installs ACLI. I think the "acquia" recipe ships with the latest version of ACLI so you don't have to install it manually, but I'm not 100% about that.
Here's the error where it tries to connect to the local database with the wrong username/password/database schema name. The default username/password/database for the "drupal10" recipe is.... "drupal10", not "drupal".
I realized that when I looked at the help documentation for the command
So I ran
After specifying those env vars, the database pull works successfully and is able to connect and import into my local database. |
I tried searching the issues, but couldn't find the same issue I'm having. I've noticed an issue with the recent version of Lando (v3.6.0) that the
lando acli pull:db
does not work like it used to.Whilst running it, I see this notice:
The default database created is setup with:
I tried adding in my default database details, but it doesn't connect to the database when trying to run the command again. Neither does the Drupal site (can't connect to the database).
Adding the default database details in the
.lando.yml
file:Not sure if I'm doing this correctly for config, any help would be appreciated on that.
The other solution seems to be working
lando pull --code=none --database=dev --files=none
which is great and might be more ideal to use, but just want to find out if this is the recommended way now so I can let my team know.The text was updated successfully, but these errors were encountered: