Skip to content

Conversation

@froboy
Copy link
Contributor

@froboy froboy commented Nov 19, 2025

This is heavily based on #6213, and related to #6180 and #5912.

It needs tests.

Working locally I was able to get things working with a drush alias config like so:

develop:
  options:
    ...
  kubectl:
    namespace: "${env.CUSTOMER_NAME}-dev"
    resource: 'deploy/${env.CUSTOMER_NAME}-dev'
    container: 'php'
    tty: true
    interactive: true
  paths:
    drush-script: /usr/src/app/vendor/bin/drush
  uri: "https://${env.CUSTOMER_NAME}-dev.k8s.myserver.net/"

@froboy froboy marked this pull request as draft November 19, 2025 16:46
@weitzman
Copy link
Member

As mentioned at #6213 (comment), I'd prefer for transport-specifics (e.g. kubectl) to stay out of the Drush codebase. Thats currently handled in consolidation/site-process.

@froboy
Copy link
Contributor Author

froboy commented Nov 19, 2025

@weitzman thanks for the feedback. I reviewed the kubectl transport PR and came across this unanswered question. Any thoughts on that? Where would rsync stuff go in consolidation/site-process?

@weitzman
Copy link
Member

rsync is a layer above Process so thats why there is no rsync stuff on consolidation/process. i dont know offhand how to structure the feature thats being suggested here. its a complex feature that is needed by relatively few users. thats why I am picky about adding the complexity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants