Hrm. Maybe I just need to dig even deeper into how Porcelain is pulling this off because their shell/2 command can do this without the use of a script. good tip on the script though. Ideally my users would be grabbing env variables in their check and handler plugins rather than trying to pass them in the check command they are doing. (I know, no context. Sorry)
beardedeagle
isaacsanders
All I know is you work for GoDaddy (from your slack description), so I imagine there might a lot of sysadmin type features you wish to support.
0
beardedeagle
Correct. This app is a monitoring service where they can create checks and a part of the check is the path to the check plugin and opts to pass to it. So allowing them to do as much as possible is the goal.
0
peerreynders
beardedeagle
isaacsanders
peerreynders
Opt =
{packet, N :: 1 | 2 | 4} |
stream |
{line, L :: integer() >= 0} |
{cd, Dir :: string() | binary()} |
{env,
Env ::
[{Name :: os:env_var_name(),
Val :: os:env_var_value() | false}]} |
{args, [string() | binary()]} |
{arg0, string() | binary()} |
exit_status |
use_stdio |
nouse_stdio |
stderr_to_stdout |
in |
out |
binary |
eof |
{parallelism, Boolean :: boolean()} |
hide
0
isaacsanders
beardedeagle
iex(16)> port = Port.open({:spawn, "/bin/echo $GOPATH"}, [:binary])
#Port<0.19>
iex(17)> flush
{#Port<0.19>, {:data, "/Users/rlthompson/go\n"}}
:spawn vs :spawn_executable. Now I feel dumb.
1
beardedeagle
And if anyone comes to this thread looking for the same thing i was, here is how you also get the status code:
iex(18)> port = Port.open({:spawn, "/bin/echo $GOPATH"}, [:binary, :exit_status])
#Port<0.20>
iex(19)> flush
{#Port<0.20>, {:data, "/Users/rlthompson/go\n"}}
{#Port<0.20>, {:exit_status, 0}}
:ok
3