@superglue/cli 1.1.15 → 1.1.17

package/dist/cli.js

@@ -2391,7 +2391,7 @@ Use parameterized queries with $1, $2, etc. placeholders:
                     
                     <div style="margin-top: 24px; padding: 20px; background: #fefce8; border-radius: 12px; border: 1px solid #fef08a;">
                       <p style="margin: 0; color: #854d0e; font-size: 14px;">
-                        <strong>\u{1F4A1} This is a demo tool!</strong> You just ran your first superglue workflow. 
+                        <strong>\u{1F4A1} This is a demo tool!</strong> You just ran your first superglue tool. 
                         Edit this tool or create your own to automate any API integration.
                       </p>
                     </div>
@@ -4661,6 +4661,54 @@ API Base URLs:
           "api key"
         ]
       },
+      datahub: {
+        name: "datahub",
+        apiUrl: "https://{your-datahub-host}",
+        regex: "^.*(datahub|acryl\\.datahub|datahubproject|datahub-gms|acryl\\.io).*$",
+        icon: "lucide:library-big",
+        docsUrl: "https://docs.datahub.com/docs/api/openapi/openapi-usage-guide",
+        preferredAuthType: "apikey",
+        keywords: [
+          "metadata",
+          "catalog",
+          "data discovery",
+          "lineage",
+          "dataset",
+          "dashboard",
+          "ml model",
+          "governance",
+          "entities",
+          "aspects",
+          "urn",
+          "relationships",
+          "schema",
+          "openapi",
+          "gms",
+          "ingestion",
+          "acryl",
+          "oidc",
+          "api key"
+        ],
+        systemSpecificInstructions: `DataHub is a metadata catalog (discovery, lineage, governance, quality, contracts). Programmatic access for REST-first workflows is the OpenAPI surface on the Metadata Service (GMS), not the marketing or docs site.
+
+OSS vs Cloud (brief): Self-hosted (open-source) means you run DataHub in your environment (Docker/K8s/Helm, etc.) and own URLs, upgrades, and networking. DataHub Cloud (Acryl) is a managed instance: you typically get https://<your-domain>.acryl.io, onboarding from the integrations team, optional AWS PrivateLink into your VPC, and UI login via admin invite or OIDC \u2014 same metadata model and APIs in principle, different hostname, auth onboarding, and who operates the plane. Always use the base URL you were given, not generic doc sites.
+
+DataHub Cloud UI access: Admin users receive an invite link; OIDC uses your IdP\u2019s Client ID, Client Secret, and Discovery URL (must resolve to \u2026/.well-known/openid-configuration). Register redirect/callback https://<your-acryl-domain>.acryl.io/callback/oidc in the IdP. As of current Cloud docs, LDAP/SAML are not supported for that login path \u2014 confirm with Acryl if your requirements differ. Support: http://support.datahub.com/
+
+Ingestion & discovery: Cloud uses push-based ingestion \u2014 run DataHub\u2019s agent inside your network so secrets stay local, with scheduled Python ingestion jobs pushing metadata to your instance. Day-to-day discovery is search and browse in the UI; OpenAPI/GraphQL/Rest.li read and write the same underlying graph.
+
+Base URL (critical): OpenAPI is under /openapi/ on the GMS origin (or the UI origin if it proxies /openapi). Local quickstart: http://localhost:8080/openapi/swagger-ui/index.html \u2014 API base is scheme+host+port only (e.g. https://gms.yourcompany.com, your Cloud hostname, or a frontend that proxies GMS).
+
+Verify the base: {base}/openapi/v3/api-docs or {base}/openapi/v3/api-docs.yaml. No global openApiUrl \u2014 in superglue, import from your instance\u2019s /openapi/v3/api-docs (or .yaml).
+
+Authentication: REST examples use Authorization: Bearer <token>. Token issuance depends on edition (PATs, OIDC/session, etc.); follow DataHub\u2019s authentication and access-token docs for your deployment.
+
+Main OpenAPI groups (paths under /openapi/): entities/v1 \u2014 upsert/read/delete entity+aspect (POST; ?createEntityIfNotExists=true for create-only; GET \u2026/latest?urns&aspectNames; DELETE ?urns&soft=). relationships/v1 \u2014 graph navigation. timeline \u2014 aspect history. platform \u2014 metadata events. v3 adds batch get (/v3/entity/{entityName}/batchGet), conditional writes, JSON Patch-style updates (see OpenAPI guide).
+
+Identifiers are URN-centric (e.g. urn:li:dataset:(...)). Also GraphQL and Rest.li \u2014 see the official API overview to pick an interface.
+
+References: https://docs.datahub.com/docs/features \u2014 product context; https://docs.datahub.com/docs/api/openapi/openapi-usage-guide \u2014 OpenAPI usage; https://docs.datahub.com/docs/managed-datahub/welcome-acryl \u2014 DataHub Cloud getting started (URL pattern, OIDC callback, ingestion); https://docs.datahub.com/docs/managed-datahub/managed-datahub-overview \u2014 OSS vs Cloud feature comparison.`
+      },
       looker: {
         name: "looker",
         apiUrl: "https://{your-domain}.looker.com/api",

package/dist/dist/cli.js

@@ -2391,7 +2391,7 @@ Use parameterized queries with $1, $2, etc. placeholders:
                     
                     <div style="margin-top: 24px; padding: 20px; background: #fefce8; border-radius: 12px; border: 1px solid #fef08a;">
                       <p style="margin: 0; color: #854d0e; font-size: 14px;">
-                        <strong>\u{1F4A1} This is a demo tool!</strong> You just ran your first superglue workflow. 
+                        <strong>\u{1F4A1} This is a demo tool!</strong> You just ran your first superglue tool. 
                         Edit this tool or create your own to automate any API integration.
                       </p>
                     </div>
@@ -4661,6 +4661,54 @@ API Base URLs:
           "api key"
         ]
       },
+      datahub: {
+        name: "datahub",
+        apiUrl: "https://{your-datahub-host}",
+        regex: "^.*(datahub|acryl\\.datahub|datahubproject|datahub-gms|acryl\\.io).*$",
+        icon: "lucide:library-big",
+        docsUrl: "https://docs.datahub.com/docs/api/openapi/openapi-usage-guide",
+        preferredAuthType: "apikey",
+        keywords: [
+          "metadata",
+          "catalog",
+          "data discovery",
+          "lineage",
+          "dataset",
+          "dashboard",
+          "ml model",
+          "governance",
+          "entities",
+          "aspects",
+          "urn",
+          "relationships",
+          "schema",
+          "openapi",
+          "gms",
+          "ingestion",
+          "acryl",
+          "oidc",
+          "api key"
+        ],
+        systemSpecificInstructions: `DataHub is a metadata catalog (discovery, lineage, governance, quality, contracts). Programmatic access for REST-first workflows is the OpenAPI surface on the Metadata Service (GMS), not the marketing or docs site.
+
+OSS vs Cloud (brief): Self-hosted (open-source) means you run DataHub in your environment (Docker/K8s/Helm, etc.) and own URLs, upgrades, and networking. DataHub Cloud (Acryl) is a managed instance: you typically get https://<your-domain>.acryl.io, onboarding from the integrations team, optional AWS PrivateLink into your VPC, and UI login via admin invite or OIDC \u2014 same metadata model and APIs in principle, different hostname, auth onboarding, and who operates the plane. Always use the base URL you were given, not generic doc sites.
+
+DataHub Cloud UI access: Admin users receive an invite link; OIDC uses your IdP\u2019s Client ID, Client Secret, and Discovery URL (must resolve to \u2026/.well-known/openid-configuration). Register redirect/callback https://<your-acryl-domain>.acryl.io/callback/oidc in the IdP. As of current Cloud docs, LDAP/SAML are not supported for that login path \u2014 confirm with Acryl if your requirements differ. Support: http://support.datahub.com/
+
+Ingestion & discovery: Cloud uses push-based ingestion \u2014 run DataHub\u2019s agent inside your network so secrets stay local, with scheduled Python ingestion jobs pushing metadata to your instance. Day-to-day discovery is search and browse in the UI; OpenAPI/GraphQL/Rest.li read and write the same underlying graph.
+
+Base URL (critical): OpenAPI is under /openapi/ on the GMS origin (or the UI origin if it proxies /openapi). Local quickstart: http://localhost:8080/openapi/swagger-ui/index.html \u2014 API base is scheme+host+port only (e.g. https://gms.yourcompany.com, your Cloud hostname, or a frontend that proxies GMS).
+
+Verify the base: {base}/openapi/v3/api-docs or {base}/openapi/v3/api-docs.yaml. No global openApiUrl \u2014 in superglue, import from your instance\u2019s /openapi/v3/api-docs (or .yaml).
+
+Authentication: REST examples use Authorization: Bearer <token>. Token issuance depends on edition (PATs, OIDC/session, etc.); follow DataHub\u2019s authentication and access-token docs for your deployment.
+
+Main OpenAPI groups (paths under /openapi/): entities/v1 \u2014 upsert/read/delete entity+aspect (POST; ?createEntityIfNotExists=true for create-only; GET \u2026/latest?urns&aspectNames; DELETE ?urns&soft=). relationships/v1 \u2014 graph navigation. timeline \u2014 aspect history. platform \u2014 metadata events. v3 adds batch get (/v3/entity/{entityName}/batchGet), conditional writes, JSON Patch-style updates (see OpenAPI guide).
+
+Identifiers are URN-centric (e.g. urn:li:dataset:(...)). Also GraphQL and Rest.li \u2014 see the official API overview to pick an interface.
+
+References: https://docs.datahub.com/docs/features \u2014 product context; https://docs.datahub.com/docs/api/openapi/openapi-usage-guide \u2014 OpenAPI usage; https://docs.datahub.com/docs/managed-datahub/welcome-acryl \u2014 DataHub Cloud getting started (URL pattern, OIDC callback, ingestion); https://docs.datahub.com/docs/managed-datahub/managed-datahub-overview \u2014 OSS vs Cloud feature comparison.`
+      },
       looker: {
         name: "looker",
         apiUrl: "https://{your-domain}.looker.com/api",

package/dist/dist/skills/superglue/SKILL.md

@@ -66,9 +66,20 @@ This prompts for:
 
 It verifies the connection before saving. On success it creates the config file, a `drafts/` directory, and updates `.gitignore` if using local config.
 
-**Option B: Environment variables (recommended for CI and AI agents)**
+**Option B: Non-interactive init (recommended for CI and AI agents)**
 
-If `sg init` is not practical (non-interactive environments, CI, AI agents), set these env vars instead:
+Pass the global `--api-key` flag to skip interactive prompts and save a config file:
+
+```bash
+sg init --api-key "your-api-key" --global
+sg init --api-key "your-api-key" --endpoint "https://custom.endpoint.com" --global
+```
+
+> **Note:** `--api-key` and `--endpoint` are global flags (not shown in `sg init --help`). They work on all subcommands including `init`.
+
+**Option C: Environment variables (no config file)**
+
+If you don't need a persistent config file, set these env vars instead:
 
 ```bash
 export SUPERGLUE_API_KEY="your-api-key"

package/dist/skills/superglue/SKILL.md

@@ -66,9 +66,20 @@ This prompts for:
 
 It verifies the connection before saving. On success it creates the config file, a `drafts/` directory, and updates `.gitignore` if using local config.
 
-**Option B: Environment variables (recommended for CI and AI agents)**
+**Option B: Non-interactive init (recommended for CI and AI agents)**
 
-If `sg init` is not practical (non-interactive environments, CI, AI agents), set these env vars instead:
+Pass the global `--api-key` flag to skip interactive prompts and save a config file:
+
+```bash
+sg init --api-key "your-api-key" --global
+sg init --api-key "your-api-key" --endpoint "https://custom.endpoint.com" --global
+```
+
+> **Note:** `--api-key` and `--endpoint` are global flags (not shown in `sg init --help`). They work on all subcommands including `init`.
+
+**Option C: Environment variables (no config file)**
+
+If you don't need a persistent config file, set these env vars instead:
 
 ```bash
 export SUPERGLUE_API_KEY="your-api-key"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@superglue/cli",
-  "version": "1.1.15",
+  "version": "1.1.17",
   "bin": {
     "sg": "./dist/cli.js"
   },

package/skills/superglue/SKILL.md

@@ -66,9 +66,20 @@ This prompts for:
 
 It verifies the connection before saving. On success it creates the config file, a `drafts/` directory, and updates `.gitignore` if using local config.
 
-**Option B: Environment variables (recommended for CI and AI agents)**
+**Option B: Non-interactive init (recommended for CI and AI agents)**
 
-If `sg init` is not practical (non-interactive environments, CI, AI agents), set these env vars instead:
+Pass the global `--api-key` flag to skip interactive prompts and save a config file:
+
+```bash
+sg init --api-key "your-api-key" --global
+sg init --api-key "your-api-key" --endpoint "https://custom.endpoint.com" --global
+```
+
+> **Note:** `--api-key` and `--endpoint` are global flags (not shown in `sg init --help`). They work on all subcommands including `init`.
+
+**Option C: Environment variables (no config file)**
+
+If you don't need a persistent config file, set these env vars instead:
 
 ```bash
 export SUPERGLUE_API_KEY="your-api-key"