Closed rudolfbyker closed 2 years ago
@greg-1-anderson Do you have any comments on how the yaml structure under kubectl in the site alias should be designed? It's currently super simple:
foo:
paths:
drush-script: /vv/vendor/bin/drush
root: /vv/web
uri: drupal.example.com
kubectl:
tty: false
interactive: false
namespace: vv
resource: deploy/drupal-deployment
container: drupal
I'm wondering whether we would ever put anything other than transport info under kubectl. But I doubt it.
Did you see my comment above? Ready to merge?
Sure, let's go ahead and put this in. Thanks.
Thanks for the merge. I see this is working well for SSH, but not for rsync commands. Any idea why/why not? Do rsync commands use a different mechanism? I don't find anything related to rsync in this repo, other than strings in the tests.
I'm trying to achieve something like this transparently: https://serverfault.com/a/887402/301389
Ideally we document this in README
Overview
This pull request:
Summary
Implement a new kubectl transport for accessing Drupal instances running in Kubernetes.
Description
If you have this alias:
... you can do this:
... or any other drush command, and it will run via kubectl, like this: