Define Command Outputs
See original GitHub issueFor each command, it would be nice if we were able to tell what the plugin was going to respond with
Let’s say I have a plugin foo
that responds to command bar
with JSON:
{
"foo": "bar",
"baz": "bat",
}
There is no good way to tell BEERGARDEN that the above if the expected output. If there was a way to tell BEERGARDEN that, we would suddenly know a lot more about how a plugin is operating, and whether or not what it responds with is expected or unexpected. This would enable-us to create a flow-based GUI/system.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
OUTPUT command - IBM
OUTPUT is a foreground-initiated-background (FIB) command. This command is generally used in conjunction with SUBMIT, STATUS, and CANCEL commands. The OUTPUT ...
Read more >Standard Output Definition - The Linux Information Project
Standard output, sometimes abbreviated stdout, refers to the standardized streams of data that are produced by command line programs (i.e., all-text mode ...
Read more >How to set commands output as a variable in a batch file
My command is "openssl dgst -sha384 -binary %1% | openssl base64 -A" and I wish the string output to be stored in a...
Read more >Workflow commands for GitHub Actions
Actions can communicate with the runner machine to set environment variables, output values used by other actions, add debug messages to the output...
Read more >BASH command output to the variable - Linux Hint
Here, `who` command will execute first that print the user's information of the currently logged in user. The output of the `who` command...
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 FreeTop 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
Top GitHub Comments
Yeah, this issue is for the long-term goal of being able to easily tie the output of one plugin to the input of another plugin. Essentially, the idea would be to enable us to create flow-based plugins without ever having to write code. Does that make any sense?
Unlikely to tackle this in the current iteration of BG. Closing for now.