Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tFtpd-00HFyB-3j for pgadmin-hackers@arkaria.postgresql.org; Tue, 26 Nov 2024 11:34:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tFtpb-006I55-RH for pgadmin-hackers@arkaria.postgresql.org; Tue, 26 Nov 2024 11:34:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tFtpb-006I4x-JU for pgadmin-hackers@lists.postgresql.org; Tue, 26 Nov 2024 11:34:11 +0000 Received: from mail-lf1-x12e.google.com ([2a00:1450:4864:20::12e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tFtpY-0047jv-Op for pgadmin-hackers@postgresql.org; Tue, 26 Nov 2024 11:34:10 +0000 Received: by mail-lf1-x12e.google.com with SMTP id 2adb3069b0e04-53dee56edceso311891e87.1 for ; Tue, 26 Nov 2024 03:34:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; t=1732620847; x=1733225647; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=BY5oQB723hjhuSBH09xSM3L4dOnV7u3WaMaT9o5u+WI=; b=cAzNoaz/Eo2QB7PDqEQ2lf4gBkaQmWRGV8s0Q+KhaLD0nHPqF95BiRenCictKA7tfn V7Yjj9R6e6hXaA6y9eroa8cKSF51L4h7ojPHOdOyBuxwhzA8og8ulAJmXiOM05q+M0XE yFnd3sgHcKkMyDPPOQjYVn5C8huv1E9gBSx++Ul7KrdzdQeOm6H3uY6fNeQHNws6wiW8 /ZQUSu9u9+aIXtFQweEwBcT/43Mn1bWMI4DTIPVqqADAXnE1cZAnW7dBpgM+mqwHx6FD B5WHJxaks1WGmCwempbA4c+kZAazlTbfYr8PuPTID3nj3bFkiEmy6/Tts2jki44KUMnm ERcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732620847; x=1733225647; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=BY5oQB723hjhuSBH09xSM3L4dOnV7u3WaMaT9o5u+WI=; b=LJ42LOdlaf4UyJxhX/XFf2VuNwmZ3BN45FYanNwCNWtWZYCjhTCHYoN6kXLOiYRooU Kfv0TZMYJJ9ItmERU8sRCF+LjterjQ348Al1P9pDNnIuzH5U5r5a8DdHYDpBayft6AVI RjIwAudPTKH9dhDEOYGs20AxPkCCshpyOEmbcSjw81w10TuySySLJMWbxY9VQmZ9zV95 6co5xFGgCFuuk9GgLBnxlS+YqnXs38OqzfVB//5TIfi5Ln2T6Pihu0PjQGVfL8L7lH6G EOK3U+mO975t+JhgnCQJsjUt4tb4NeyHhkTSj0nPXN12lcsKv3Bd18qlIqn9c1sTCDK3 9zjw== X-Forwarded-Encrypted: i=1; AJvYcCVHBx6ffoFAVuLDY2BJeuR3wncI/gB4Itqcnr80De+Bue/cwSDYMg8oLTw3vMeFP0UvW2h1fp0MtI3jACZDqBU=@postgresql.org X-Gm-Message-State: AOJu0YzJDg6hUxp62GWFZcm7TujavE9m9++x1/iSjX+cwxwyNWVi1m1A mywvsAi1ieBdI4MBspJTKkm7kpr6Zjs73uCjCi1PnMJjnQHDUxdMqKFgcTiGvmf7HHIsAjDiF2p zo9J1WSRBciGFk2n2ltVoUuVnEoY04iF5fSSy X-Gm-Gg: ASbGncuefsSCAsl5feFZxuLXwmnY0f8laHdXswEJNxDwnQLdxEZopXodmNK01hRt/ZH FPKB3ifMhcz1RgG0lVfnCCaL5qh/0oA== X-Google-Smtp-Source: AGHT+IHVXq3j1xTjyaJQt09NySf2uEG8lHXKRqtja30bFnS3THOWnHKcKmmRidYD9t2Yif1xr1OKQg1DTP1jxGBFY4A= X-Received: by 2002:a05:6512:3f15:b0:53d:ed6d:71cc with SMTP id 2adb3069b0e04-53ded6d724cmr670234e87.8.1732620847375; Tue, 26 Nov 2024 03:34:07 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Dave Page Date: Tue, 26 Nov 2024 11:33:56 +0000 Message-ID: Subject: Re: Require suggestions on feature 6794 To: Aditya Toshniwal Cc: Pravesh Sharma , pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000238d800627cf3acc" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000238d800627cf3acc Content-Type: text/plain; charset="UTF-8" On Tue, 26 Nov 2024 at 11:30, Aditya Toshniwal < aditya.toshniwal@enterprisedb.com> wrote: > Hi Pravesh, > > In addition to that, why do we need env vars at all? We can simply pass > them as arguments to passexec script. It's up to the users to use it or > ignore it. > Or do some string substitution in the command, e.g. /path/to/passexec.sh $HOST$ $PORT$ or similar, so the user has even more flexibility. I know that is done in PEM in a few places, possibly in pgAdmin too, though I don't recall offhand (if it is, we should be consistent on how the parameters are notated). -- Dave Page pgAdmin: https://www.pgadmin.org PostgreSQL: https://www.postgresql.org pgEdge: https://www.pgedge.com --000000000000238d800627cf3acc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Tue, 26 Nov 2024 at 11:30, Aditya = Toshniwal <aditya.t= oshniwal@enterprisedb.com> wrote:
Hi Pravesh,

In addition to that, why do we need env vars at all= ? We can simply pass them as arguments to passexec script. It's up to t= he users to use it or ignore it.

Or do some string substitution in the command, e.g.

/path/to/passexec.sh $HOST$ $PORT$

or similar,=C2=A0so the user has even more flexibility. I know tha= t is done in PEM in a few places, possibly in pgAdmin too, though I don'= ;t recall offhand (if it is, we should be consistent on how the parameters = are notated).

--=
--000000000000238d800627cf3acc--