Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bjV0H-0000Y5-0M for pgadmin-hackers@arkaria.postgresql.org; Mon, 12 Sep 2016 17:26:45 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bjV0G-00010V-JK for pgadmin-hackers@arkaria.postgresql.org; Mon, 12 Sep 2016 17:26:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bjV02-0000T4-R9 for pgadmin-hackers@postgresql.org; Mon, 12 Sep 2016 17:26:31 +0000 Received: from mail-qk0-x22c.google.com ([2607:f8b0:400d:c09::22c]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bjUzz-0008JZ-Kg for pgadmin-hackers@postgresql.org; Mon, 12 Sep 2016 17:26:30 +0000 Received: by mail-qk0-x22c.google.com with SMTP id w204so149442654qka.0 for ; Mon, 12 Sep 2016 10:26:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=2f46J+vN+Td7kjDD8O2ARRwO00CqWuNM5Omum8DyuNM=; b=bHJIXMPCpXguNftcJSmHfd8u8+puSFtI+2Qsi/tTEJNgY7G+c6XtIdIv2TWD+n2Lme rbMLfddN96LeBMD2Pof5QzvxaMM6d34Lw7rMcyfsC8tABdNBWKEUcuG6Q1Fiy39lWtBP bkor/n2EjXVEZI+OGHOhMaNeoJAYDj76UkEp1xyL/LwnSHgdR624wl34AYDso4DRlfw8 PkBSobM6EeU67nwJqpvlnUwcrhFDtAmp90UxxaO9IRrCrTH/0sD/lQTRLvaBpOixnGhS 2HRHsXkZ35+ioeO138mtEDbm3e2t8Lr//vZCk+sG7IULWiCmqDqsl9HXas0tSV7LnqPm ZAZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=2f46J+vN+Td7kjDD8O2ARRwO00CqWuNM5Omum8DyuNM=; b=Rh4pLJ+envMn5KP9netZXgBwGIeXUmhLlB2pVvO5lyYyRcbRoXsJUTSD218+IRsyMU XlhH3tPbPWiKP5H+wGldHUZjhDZxceC6s3R9KgK7m6XZ8p5Jd2SGNjc0YG57hcA3ZLZQ OmS4OsYK4wm8aJpqBpsZWGczJtHqF9hwXD2zM3AUPH9cdJb5FC7ufdvPm75ulGdp8Tp5 dGsYLPNR5pExjP+u3qvHe6v2zzrPvJa1QmLxqtLbZPHtcNpvJH2DoT3PkBvidhv1gkOf uiC65Ozt3ee0HOkK8oXi7+WCrJxodRlBqgBhfSstXbywCIWZ4YjHzU5XFrEwfJqCwD/y 3ruA== X-Gm-Message-State: AE9vXwOvH8A73tK1UpOlug3sAg7M4yVNb9iAwCc1TrZ/Uqo9QaHcHQ1b2rYg2k2aQULEW3lEykAoNJNtgRbqvxE+ X-Received: by 10.55.210.67 with SMTP id f64mr8008061qkj.166.1473701181016; Mon, 12 Sep 2016 10:26:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.41.114 with HTTP; Mon, 12 Sep 2016 10:26:20 -0700 (PDT) From: Navnath Gadakh Date: Mon, 12 Sep 2016 22:56:20 +0530 Message-ID: Subject: Server specific advanced config file for testsuite To: Dave Page Cc: Kanchan Mohitey , pgadmin-hackers Content-Type: multipart/alternative; boundary=94eb2c04e53a66b0c6053c52cb4d X-Pg-Spam-Score: -2.3 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org --94eb2c04e53a66b0c6053c52cb4d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Dave, As we know that, we are using two JSON files one is for basic configuration of server(test_config.json) and second for detailed configuration of server(test_advanced_config.json). In test_advanced_config.json, we give detail for database, schema, extension, collation etc. These details are generic I mean these details are not server specific. - Do we need to allow user to give server specific details? If yes, there should be some identification(like =E2=80=98server_type=E2=80= =99, =E2=80=98version=E2=80=99) for each detail so that we can read server appropriate details. We have one approach in mind, to attach 'server_type' & 'version' to each detail So, modified test_advanced_config.json can be like this, { "add_database_data=E2=80=9D:[ { "conn_limit": -1, =E2=80=9Cowner=E2=80=9D: =E2=80=9Cpostres=E2=80=9D, . . . . =E2=80=9Cserver_type=E2=80=9D: =E2=80=9Cpg=E2=80=9D, =E2=80=9Cversion=E2=80=9D: =E2=80=9Cpg9.4=E2=80=9D }, { { "conn_limit": -1, =E2=80=9Cowner=E2=80=9D: =E2=80=9Centerprisedb=E2=80=9D, . . . . =E2=80=9Cserver_type=E2=80=9D: =E2=80=9Cppas=E2=80=9D, =E2=80=9Cversion=E2=80=9D: =E2=80=9Cppas9.6=E2=80=9D } }], =E2=80=9Cschema_credentials=E2=80=9D: [{"func_acl": [], "seq_acl": [], . . . . =E2=80=9Cserver_type=E2=80=9D: =E2=80=9Cpg=E2=80=9D, =E2=80=9Cversion=E2=80=9D: =E2=80=9Cpg9.4=E2=80=9D }] . . . . . } Any suggestions? For multiple server currently we used 'owner' to identify the server, but that fails if two servers have the same owner. --=20 Thanks, Navnath Gadakh Software Engineer EnterpriseDB Corporation Mobile: +91 9975389878 --94eb2c04e53a66b0c6053c52cb4d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Dave,
=C2=A0 =C2=A0 =C2=A0As we know tha= t, we are using two JSON files one is for basic configuration of server(test_config.json) and second for detailed configuration of server(test_advanced_config.j= son).
In test_a= dvanced_config.json, we give detail for d= atabase, schema, extension, collation etc. These details are generic I mean these det= ails are not server specific.=C2=A0
- Do we need to allow user to give server specific details?
If yes, t= here should be some identification(like =E2=80=98server_type=E2=80=99, =E2=80=98version=E2=80=99) fo= r each detail=C2=A0so that we can read server appr= opriate details.
We have one approach in mind, to attach 'ser= ver_type' & 'version' to each detail
So, modified= test_advanced_config= .json can be like this,
{
"add_d= atabase_data=E2=80=9D:[
{
=C2=A0"conn_limit": -1,
=C2=A0=E2=80=9Cowner=E2=80=9D: =E2=80=9Cpostres=E2=80=9D,
=C2=A0 .
=C2=A0 .
=C2=A0 .
=C2=A0 .<= /font>
=C2=A0=E2=80=9Cserver_= type=E2=80=9D: =E2=80=9Cpg=E2= =80=9D,
=C2=A0=E2=80= =9Cversion=E2=80=9D: =E2=80=9Cpg9.4=E2=80=9D
},
{
{
=C2=A0"conn_limit": -1,
=C2=A0=E2=80=9Cowner=E2=80=9D: =E2=80=9Centerprisedb=E2=80=9D,
=C2=A0 = .
=C2=A0 .
=C2=A0 .
=C2=A0 .
=C2=A0=E2=80=9Cserver_type=E2=80=9D: =E2=80=9Cppas=E2=80=9D,
=C2=A0=E2=80=9Cversion=E2=80=9D: =E2=80=9Cppa= s9.6=E2=80=9D
}
}],=
=E2=80=9Cschema_crede= ntials=E2=80=9D:
[{&qu= ot;func_acl": [],
=C2=A0 "seq_acl": [],
=C2=A0 .
= =C2=A0 .
=C2=A0 .
=C2=A0 .
= =C2=A0 =E2=80=9Cserver_type=E2=80=9D: = =E2=80=9Cpg=E2=80=9D,
=C2=A0 =E2=80=9Cversion= =E2=80=9D: =E2=80=9Cpg9.4=E2=80=9D=C2=A0
}]
.
.
.
=
.
. =C2=A0
}

Any suggestions?
For multiple server currently we used 'owner' to ident= ify the server, but that fails if two servers have=C2=A0the same owner.

--
=
Thanks,
Navnath=C2=A0Gadakh
=
Software Engineer
EnterpriseDB Corporation
Mobile: +91 9975389878=C2=A0


--94eb2c04e53a66b0c6053c52cb4d--