-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Use --format=json in sql:sync #3936
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
Conversation
|
LGTM as long as its been tested against Drush 9.5 and Drush 8. |
|
I tried to test this, remote drush is 8 (global) but we also have a project-relative drush 9. |
|
It should be safe to go from Drush 9 (local) -> global Drush 8 (remote) -> site local Drush 9. Removing the global Drush 8 is an option, but the inconvenience here is that you need to set %drush-script in all of your aliases. |
|
@larowlan What is the output of the sql:sync with --debug? |
Note I have |
|
@larowlan Try: It's also okay to use |
|
spoke too soon |
|
|
|
Thats actually how Drush9 does it. See drush/src/Commands/sql/SqlSyncCommands.php Lines 140 to 144 in 9dacc08
|
|
the local is this branch, remote is now 9.5.2 |
|
OK I forgot all about |
|
No hurry @greg-1-anderson i've got a workaround in our Makefile that uses ssh/rsync etc Happy to keep lending a hand testing |
|
@larowlan : Looked at this a bit more. I was able to successfully run an sql-sync from a Drupal site with a site-local Drush 9.5 to a Drupal site with a site-local Drush 9.6 when both sites were local. It appears that the bug you are seeing is limited to remote-source sites with Drush 9.5 (or earlier). Your error says "Site alias @self.dev not found." What is your sql-sync commandline? Does it include @self.dev? It looks like |
|
I was running |
|
@larowlan Do you have your |
|
Yes
…On Wed, Mar 6, 2019, 2:44 PM Greg Anderson ***@***.***> wrote:
@larowlan <https://github.com/larowlan> Do you have your @dev alias
defined in self.sites.yml?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3936 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAh49s7VTaID39jHzSmKXyuqES3nYxWnks5vT0eogaJpZM4a_ufe>
.
|
4ddaadf to
a3224c5
Compare
|
@larowlan I think I was able to reproduce and fix the problem preventing |
2fc7a3e to
b4520e5
Compare
composer.json
Outdated
| "consolidation/output-formatters": "^3.3.1", | ||
| "consolidation/robo": "^1.4.6", | ||
| "consolidation/site-alias": "^3.0.0-beta1", | ||
| "consolidation/site-alias": "dev-find-self-site as 3.0.0-beta1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clever ... change this before merge?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I want feedback on this PR before I merge the site-alias PR, but I will merge and make a beta2 release before I merge here.
| except: | ||
| - gh-pages | ||
| only: | ||
| - master |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
still tests PRs before they merge?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. Without the branch limitation, pull requests are tested twice.
|
Tested this and it seems to be working fine. I will merge this after I make the stable releases of site-alias 3.0.0 and site-process 2.0.0, probably tomorrow morning. |
…ntials in sql:sync. Make '@self' aliases more discoverable.
b4520e5 to
071a878
Compare
|
Released another beta of site-alias |
Use format json instead of format string when fetching database credentials in sql:sync