Support pipe into commands
See original GitHub issueLet’s assume somebody wants to write the following command spo site list | spo app install (imagine some filters in the site collection selection and an app id provided).
Today that’s not possible because commands don’t support pipe input.
More context https://github.com/pnp/office365-cli/pull/624#issuecomment-426727846
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:16 (16 by maintainers)
Top Results From Across the Web
Working with pipes on the Linux command line - Red Hat
One of the most powerful shell operators is the pipe ( | ). The pipe takes output from one command and uses it...
Read more >Pipe (|) support in show commands - Aruba Networks
The pipe (|) command is a CLI session command that filters the output of show show commands according to the criteria specified by...
Read more >PIPE command - IBM
The PIPE command is a powerful and flexible command that lets you issue commands and manipulate messages in a pipeline. Many of the...
Read more >Pipe Support Place Commands - PDS - Help
The Place commands are used to place pipe supports, copy pipe supports, place physical pipe support, and place local pipe support. Place Pipe...
Read more >supporting pipes for shell in c - Stack Overflow
For a class, I need to create my own shell in C. I'm trying to support piping of commands using pipelines. As far...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@andrewconnell and I had a discussion about this lately and we couldn’t find examples of other CLIs doing this. It seems like such behavior (piping complex output of one command to another) is something specific to PowerShell. CLIs are typically used in scripts where the values are assigned to and passed via variables. So while adding support for piping could be done, it might be confusing for folks who are used to working with CLIs. I’m inclined to reconsider adding this to the CLI and keep using scripts for more complex scenarios
Closing this for now as we don’t have a specific use case for implementation. Let’s revisit in the future if need be.