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 1tFtgD-00HEz4-2c for pgadmin-hackers@arkaria.postgresql.org; Tue, 26 Nov 2024 11:24:29 +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 1tFtg9-006Ee0-5M for pgadmin-hackers@arkaria.postgresql.org; Tue, 26 Nov 2024 11:24:25 +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 1tFtg8-006Edm-UW for pgadmin-hackers@lists.postgresql.org; Tue, 26 Nov 2024 11:24:24 +0000 Received: from mail-lj1-x22b.google.com ([2a00:1450:4864:20::22b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tFtg5-0047fe-V2 for pgadmin-hackers@postgresql.org; Tue, 26 Nov 2024 11:24:24 +0000 Received: by mail-lj1-x22b.google.com with SMTP id 38308e7fff4ca-2ffbea0acc2so24508181fa.1 for ; Tue, 26 Nov 2024 03:24:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; t=1732620260; x=1733225060; 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=8C/9igdY+GBV9IyrDz6peo0CmBAMcBR6YAf0HcvOPWk=; b=bGTFsIEgtPRVBO9Ty/Rd/Gk+tQzOmPj/tyXf5WDEdEusAPHFPQy7FfGNjabRcm97Wz UMRlPYnKRqkbrJUFtQDLPZz96R6F+QjBNhemFUGqQBuIoARHovBYAafvuScCJGJ8cXRx q671SGI8sEfVoyDKAeAMAv2kmoYuExTi7mX9WKb++RTdTFshr7pkxYDEc3eXSGngWYeO 4pVGy5Aic6Q3gJ+bWTbpol805mwAVm4AYeD9nojMfimMNVIa0zIVJ9Ho0GaQaaNHK2eB FkWgl1pcP6j5UfJcAwRZgMdpH43Wro1SScHWiSxkgVpNs0tknv09fwZMrI6Zvc4AYK0w T2Ng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732620260; x=1733225060; 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=8C/9igdY+GBV9IyrDz6peo0CmBAMcBR6YAf0HcvOPWk=; b=X+O+U2Sb4PJU6PrnGPNJp/aMnX+wMgIzKfB2CdhbhM8WoNKol5CNTUdK659Vj0CCW8 E6rd+PAu73GqXH/3vQpCxgWO7+LTea23XeVPSeX02MVJiXbvcQoyAD5hiL9k1gNin0+J EcWaHWLdlIuO9gIHpZBXwRiucyrO2cqj4/348Ck0s+BYyU+EcIF2Ex+B3oCUXNs0gQQI f3k6yRsc2CgYbnZgt+C8Vy9VpBm/SOIM2A2L1bpN0446giIGLmKKipLDgfSgNIs33Kgw 7xOov+RyxL0/JlibxVvbGKJgJ+2bODGmbX+iXM/guTyypgpbtq0nbsNZ9Sf81KR06hE3 Idsw== X-Gm-Message-State: AOJu0YzM6oXxuYTiCtyXG1NP5j8AaRGPMqS8ApjDfdDarzO763xQIvWs qcRBQrIr5dktxKvcjHMjsrCaeFDuElQbkm8SYSlQJLWrpWENev2nIDLRSrDEUYjORTrzcN+D0NM Dup2UtRSxQhYxp/9wVXbYdwEQfWcUQEdPOA+Fh2Bxx5x157C80g== X-Gm-Gg: ASbGncs1uD94S4t+F1Swe4MefTsmNnEzZavmTZO4GOSl11Um3uN8QbNaACU96oz8Bb1 RrB5+X2UpXY1ABPwRrticI2hlb8nvXA== X-Google-Smtp-Source: AGHT+IGmn0jpTGGTgGbBt9OgWEalNV7fnN23b3zwk5kg6Hg3OrGms1xx6iJkjq6Hbi7/1h81l57tGimARSn7IOKcgC8= X-Received: by 2002:a05:651c:b2c:b0:2ff:cf77:a28c with SMTP id 38308e7fff4ca-2ffcf77a3b9mr7546481fa.40.1732620260346; Tue, 26 Nov 2024 03:24:20 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Dave Page Date: Tue, 26 Nov 2024 11:24:09 +0000 Message-ID: Subject: Re: Require suggestions on feature 6794 To: Pravesh Sharma Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="0000000000002625330627cf17e9" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002625330627cf17e9 Content-Type: text/plain; charset="UTF-8" Hi On Tue, 26 Nov 2024 at 10:55, Pravesh Sharma < pravesh.sharma@enterprisedb.com> wrote: > Hi Dave/Team > > I have started working on feature #6794 > . The user wants to > pass connection information, such as host, port, and username, to the > passexec command without hardcoding these values. I plan to implement it as > follows: The user will set environment variables for the host, port, and > username, and before running the passexec command, we will replace the > corresponding values with the environment variables. > > > Please share your suggestions or feedback on the approach I am proposing. > I'm not sure why the user would need to set environment variables - wouldn't pgAdmin just set them in the environment of the passexec process, based on the server definition? -- Dave Page pgAdmin: https://www.pgadmin.org PostgreSQL: https://www.postgresql.org pgEdge: https://www.pgedge.com --0000000000002625330627cf17e9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi

On Tue, 26 Nov 2024 at 10:55, Pravesh Sharma <pravesh.sharma@enterprised= b.com> wrote:
Hi Dav= e/Team

I have started working on feature #6794. The user wants to pass connection information, such as host,= port, and username, to the passexec command without hardcoding these value= s. I plan to implement it as follows: The user will set environment variabl= es for the host, port, and username, and before running the passexec comman= d, we will replace the corresponding values with the environment variables.=


Please share your suggestions or feedback on the ap= proach I am proposing.


I= 9;m not sure why the user would need to set environment=C2=A0variables - wo= uldn't pgAdmin just set them in the environment of the passexec process= ,=C2=A0based on the server definition?

--
--0000000000002625330627cf17e9--