Skip to content
This repository has been archived by the owner on May 8, 2023. It is now read-only.

Allow piped commands when "stop"ing a server #179

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mkilpatrick
Copy link
Contributor

The current ParseCommand assumes that only one command and single
list of arguments will exist. This means that piped commands will
not work. This adds support for allowing piped commands for any
"stop" command.

Note that this does not change the build and launch commands.

list of arguments will exist. This means that piped commands will
not work. This adds support for allowing piped commands for any
"stop" command.

Note that this does not change the build and launch commands.
return nil, errors.WithStack(err)
}
cmdTokens := commandline.TokenizeCommand(b.Backend.Commands.Stop)
byteString, err := pipes.RunStrings(cmdTokens...)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we use AssemblePipes to integrate this into ConstructCommand directly?
Would be nice not to have such differing behavior between the different commands.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants