Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mlHh0-0004u9-N3 for pgsql-www@arkaria.postgresql.org; Thu, 11 Nov 2021 21:33:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mlHgy-0000hK-Qc for pgsql-www@arkaria.postgresql.org; Thu, 11 Nov 2021 21:33:08 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mlGR3-0002Qi-3r for pgsql-www@lists.postgresql.org; Thu, 11 Nov 2021 20:12:37 +0000 Received: from mail-pj1-x1031.google.com ([2607:f8b0:4864:20::1031]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mlGR0-0002pc-CF for pgsql-www@postgresql.org; Thu, 11 Nov 2021 20:12:35 +0000 Received: by mail-pj1-x1031.google.com with SMTP id np3so4942842pjb.4 for ; Thu, 11 Nov 2021 12:12:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=turbot.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=8i0vORBcu4r3U4Hs+UzRu95aqV2DHIZj6s3ML8fQZz0=; b=MfuLxGS+sikKq574GKiuA8FylkdyldUdIfprIctZ9V3lbLD2qUB+0ReNH7jWsKxjG9 eHM3m7bHHoQ7+y+fP5attESUzCVoi8VW/QW5FpFJOONDxkrokk0G3GBfcgvK8GEcFjNu c+lHnNMaeMJCnoYuvXnQ1VFvfou90TAj5TKEBRXsrwkpHDNUBaGDlcaikLE+3FByi8ui Kc3rle8CK6vWutKWySmjs5r2OqjuCUruBxJKy1Bd4ijNOk05W7fA0/BqYhyjDXld+nw6 TTsVeqgMnuHTrBCz3WIb6CEVubE7A5H89PHG7jkY2H3uBoWzB8D1MYZFIwDADn2rmk/k rMvw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=8i0vORBcu4r3U4Hs+UzRu95aqV2DHIZj6s3ML8fQZz0=; b=uIJJw7xP7F6yR1vJbNJHMZi6z66C5xNaSQqSTWZ7ZlqJMqrWVsjcr48lOBGa4xHqFN nCvjYJkKUd/8HasvvrbIuDcci3D8iPKpvAaAlRxZ2SRWg+ZTKhb+yxRgSGr+b3+eWuWF CxcBDCQfc+y4Zoc4KXWDZovB4iVfkTSYEkCodg0TFo9ufxBms4yaodmlgz73TGIPkvK3 R0VqfNn+iSB+YVl+FiqVsIzR+aIdE9LGgkLwhEcLawkt9sqBxwjWqVPfTOV/IMlkJkRd 7cKDPqHonnX8OhEklEGlIjS01LHhmg4ItEEWtCBBQLEDg70l+T/K1ZUqtlYt7mRYS+Ao vaog== X-Gm-Message-State: AOAM530bQREm75jDgUhe8JGIu7v2VeaqdGH119tG51HWhulCXTv6w6J9 DaANe78lUkQDAR6XFQ7pgOJGaKl/S35C1Z+s8AVCXd2lSPzZhNA8 X-Google-Smtp-Source: ABdhPJxRqbpmkSLx49HRcVTOYyU4XaVKfO5ScXUDKlPsDCC81OXj/KGeaSMFehNWZEhnDDNvHrHxw1BkXfspmWgtUUo= X-Received: by 2002:a17:90a:e012:: with SMTP id u18mr29610454pjy.103.1636661552750; Thu, 11 Nov 2021 12:12:32 -0800 (PST) MIME-Version: 1.0 From: Jon Udell Date: Thu, 11 Nov 2021 12:12:19 -0800 Message-ID: Subject: listing Steampipe on https://wiki.postgresql.org/wiki/Foreign_data_wrappers To: pgsql-www@postgresql.org Content-Type: multipart/alternative; boundary="000000000000783a2405d088f620" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000783a2405d088f620 Content-Type: text/plain; charset="UTF-8" Hi there, We'd like to list our tool, https://steampipe.io, on that page. We imagine it could appear under Generic SQL Database Wrappers like so: Data source: APIs (https://hub.steampipe.io/plugins) Type: Native License: Tool and FDW engine: AGPL, Plugins: Apache 2.0 Code: https://github.com/turbot/steampipe, https://github.com/turbot/steampipe-postgres-fdw, https://github.com/turbot/steampipe-plugin-* Install: https://steampipe.io/downloads Doc: https://steampipe.io/docs Notes: Steampipe bundles Postgres with an FDW engine, https://github.com/turbot/steampipe-postgres-fdw, that supports a growing ecosystem of plugins (https://hub.steampipe.io/plugins) that consume APIs, map them to tables, and enable queries within and across APIs. We'll defer to your judgement as to where and how to place it, but we hope you'll agree that Steampipe belongs on the page. Thanks, Jon Udell Steampipe community lead --000000000000783a2405d088f620 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi there,

W= e'd like to list our tool, https://ste= ampipe.io, on that page. We imagine it could appear under Generic SQL D= atabase Wrappers like so:






= Doc: https://steampipe.io/docs

Notes: Steampipe bundles Postgres with an FDW engine= , https://gith= ub.com/turbot/steampipe-postgres-fdw, that supports a growing ecosystem= of plugins (https://hub.steam= pipe.io/plugins) that consume APIs, map them to tables, and enable quer= ies within and across APIs.

We'll defer to you= r judgement as to where and how to place it, but we hope you'll agree t= hat Steampipe belongs on the page.

Thanks,

Jon Udell
Steampipe community lead

--000000000000783a2405d088f620--