docker scheme: working-directory and stdin passing (reroll of #5974) #6057
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#5974 reroll
docker exec
anddocker-compose exec
provide an option to cleanly set the working directory before running a command=> Use it instead and use
cd <...> ;
command-prefixing in vagrant/ssh casesUsing
docker
scheme,wp post update 1 - <<<foo
didn't worked (issue passing stdin to command for docker-based WP instances #4972)-t
is passed with no ability to inhibit this-i
flag is necessary=> As such:
-i
(--interactive
) is introduced (with sensible autodetection)WP_CLI_DOCKER_NO_TTY
andWP_CLI_DOCKER_NO_INTERACTIVE
environment variables are introduced to optionally inhibit these respective flagsSpecial case to handle
behat
runs (see #5974)