From 3cf7d097a82bd0e1931a44abfabdad2982b0c5c8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Anders=20F=20Bj=C3=B6rklund?= <anders.f.bjorklund@gmail.com>
Date: Thu, 15 Nov 2018 21:36:21 +0100
Subject: [PATCH] Allow setting the bridge with an env var

Gets tedious to always use: --bridge="$VARLINK_BRIDGE"

Better if it can be given as an environment variable.
---
 tool/cli.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/tool/cli.c b/tool/cli.c
index 33ccc86..55ec4a0 100644
--- a/tool/cli.c
+++ b/tool/cli.c
@@ -438,6 +438,7 @@ long cli_run(Cli *cli, int argc, char **argv) {
                 .timeout = -1
         };
         const CliCommand *command;
+        char *bridge;
         long r;
 
         r = cli_parse_arguments(argc, argv, &arguments);
@@ -447,6 +448,9 @@ long cli_run(Cli *cli, int argc, char **argv) {
         if (arguments.activate)
                 cli->activate = arguments.activate;
 
+        if ((bridge = getenv("VARLINK_BRIDGE")) != NULL)
+                cli->bridge = bridge;
+
         if (arguments.bridge)
                 cli->bridge = arguments.bridge;