@loxtep/sdk 0.7.7 → 0.7.10

package/docs/getting-started.md

@@ -1,24 +1,25 @@
 # SDK Getting Started Guide
 
-Get from zero to your first event in under 5 minutes. This guide walks you
-through installing the Loxtep SDK, authenticating, and writing your first event
-to a data product — all with a single method call.
+Get from zero to a working Loxtep workspace: authenticate, scaffold a project,
+attach to a runtime instance, and generate typed constants. Stream read/write
+comes **after** you deploy a workflow that publishes a data product.
 
-> **Other paths:** This guide covers the **programmatic SDK** path (no
-> `loxtep init` required). For **code-first workflow authoring**, see the
-> [Code-first CLI guide](./code-first-cli.md) (`init → attach → generate → test → deploy`).
-> Loxtep also supports an [Agent-first (MCP)](https://github.com/LoxtepInc/loxtep-plugins-skills)
-> path and a **Web UI** at [app.loxtep.io](https://app.loxtep.io). See the
-> [Loxtep Quickstart](https://docs.loxtep.io/quickstart) for all paths.
+> **Other paths:** [Code-first CLI](./code-first-cli.md) (`init → attach →
+> generate → test → deploy`), [Agent-first MCP](https://github.com/LoxtepInc/loxtep-plugins-skills),
+> or the **Web UI** at [app.loxtep.io](https://app.loxtep.io).
+> Overview: [Loxtep Quickstart](https://docs.loxtep.io/quickstart).
 
 ## Table of Contents
 
 - [Prerequisites](#prerequisites)
 - [Step 1: Install the SDK](#step-1-install-the-sdk)
 - [Step 2: Log In](#step-2-log-in)
-- [Step 3: Write Your First Event](#step-3-write-your-first-event)
-- [Step 4: Read Events Back](#step-4-read-events-back)
-- [Complete Example](#complete-example)
+- [Step 3: Scaffold a Workspace](#step-3-scaffold-a-workspace)
+- [Step 4: Attach to an Instance](#step-4-attach-to-an-instance)
+- [Step 5: Generate Typed Constants](#step-5-generate-typed-constants)
+- [Step 6: Explore the Platform](#step-6-explore-the-platform)
+- [Step 7: Use the SDK in Application Code](#step-7-use-the-sdk-in-application-code)
+- [Step 8: Write and Read Events (after deploy)](#step-8-write-and-read-events-after-deploy)
 - [Troubleshooting](#troubleshooting)
 - [Next Steps](#next-steps)
 
@@ -26,31 +27,27 @@ to a data product — all with a single method call.
 
 ## Prerequisites
 
-Before you begin, make sure you have:
-
 | Requirement | Details |
 |-------------|---------|
-| **Node.js 22+** | Required for the Node.js SDK (`@loxtep/sdk`). Check with `node --version`. |
-| **Loxtep account** | You need an account with the **developer** role. Ask your org admin if you don't have one. |
-| **A deployed data product** | Your organization must have at least one data product deployed to an instance. |
+| **Node.js 22+** | Required for `@loxtep/sdk`. Check with `node --version`. |
+| **Loxtep account** | Sign up at [app.loxtep.io](https://app.loxtep.io). |
+| **Runtime instance** | Your org needs at least one instance (`loxtep instances list`). New trials usually include a shared dev instance. |
+
+You do **not** need an existing data product on day one. Empty lists after
+attach are normal until you deploy workflows.
 
 ---
 
 ## Step 1: Install the SDK
 
-```bash
-pnpm add @loxtep/sdk
-```
-
-Or with your preferred package manager:
+Create a directory for your project, then install:
 
 ```bash
-npm install @loxtep/sdk
-# or
-yarn add @loxtep/sdk
+mkdir my-loxtep-app && cd my-loxtep-app
+pnpm add @loxtep/sdk
 ```
 
-Verify the installation:
+Verify the CLI:
 
 ```bash
 pnpm exec loxtep --version
@@ -60,270 +57,224 @@ pnpm exec loxtep --version
 
 ## Step 2: Log In
 
-Authenticate with your Loxtep account. This stores credentials locally so the
-SDK can make API calls on your behalf.
-
 ```bash
 pnpm exec loxtep login
+pnpm exec loxtep whoami
 ```
 
-Follow the prompts to enter your email and password. On success you'll see:
-
-```
-✓ Logged in successfully. Credentials saved to ./.loxtep/credentials.json
-```
+On success, credentials are stored in `./.loxtep/credentials.json` (project-local
+by default). `whoami` should print your email and organization — not placeholders.
 
-**Alternative: use an environment variable.** If you're running in CI/CD or a
-container, set the token directly instead of using `loxtep login`:
+**CI / headless:**
 
 ```bash
+pnpm exec loxtep login --email you@company.com --password '…'
+# or
 export LOXTEP_AUTH_TOKEN="your-jwt-token"
 ```
 
-The SDK checks `LOXTEP_AUTH_TOKEN` first, then `./.loxtep/credentials.json`
-(walking up from cwd), then `~/.loxtep/credentials.json`.
-
 ---
 
-## Step 3: Write Your First Event
-
-With the new data-product-centric API, you write events by referencing a data
-product by name. The SDK resolves all the plumbing (queue names, bot IDs, stream
-bus configuration) automatically.
+## Step 3: Scaffold a Workspace
 
-```typescript
-import { LoxtepClient } from '@loxtep/sdk';
+```bash
+pnpm exec loxtep init
+```
 
-const client = new LoxtepClient({
-  api_url: process.env.LOXTEP_API_URL,
-  auth: { type: 'jwt', token: process.env.LOXTEP_TOKEN },
-});
+Optional starter template:
 
-// Write events to a data product by name (top-level — preferred since v0.7.0)
-const writer = await client.get_writer('my-data-product');
-writer.write({ id: '123', name: 'Alice' });
-await writer.close();
+```bash
+pnpm exec loxtep init --template shopify-orders
 ```
 
-That's it. No workflow IDs, no deployment lookups, no queue name conventions.
-The SDK resolves the data product's runtime bindings, connects to the correct
-stream bus, and writes directly to the data product queue.
+This creates:
 
-### What happens under the hood
+| Path | Purpose |
+| --- | --- |
+| `.loxtep/project.json` | Project identity; updated by `attach` |
+| `workflows/` | Workflow modules you author and deploy |
+| `connectors/`, `domains/`, `data-products/` | Code-first resource folders |
 
-1. The SDK looks up the data product by name via the platform API
-2. It resolves the runtime configuration (queue, bot identity, stream config)
-3. It connects to the stream data plane and returns a writer pointed at the correct queue
+`init` can run before or after `login`. Platform project registration happens
+when you're authenticated; local scaffolding always succeeds.
 
-### Writer options
+---
 
-You can customize the writer behavior with an options object:
+## Step 4: Attach to an Instance
 
-```typescript
-const writer = await client.get_writer('my-data-product', {
-  bot_id: 'custom-bot-id',   // Override the resolved bot identity
-  batch_size: 500,            // Events per batch (default: 100)
-  max_retries: 5,             // Retry attempts on failure (default: 3)
-});
-```
+List instances, then bind your workspace to one:
 
----
+```bash
+pnpm exec loxtep instances list
+pnpm exec loxtep attach --instance <instance-id>
+```
 
-## Step 4: Read Events Back
+`attach` writes `instance_id` and `api_url` into `.loxtep/project.json`.
+Required before `generate`, `test`, and `deploy`.
 
-Reading from a data product is just as simple:
+---
 
-```typescript
-const reader = await client.get_reader('my-data-product');
+## Step 5: Generate Typed Constants
 
-for await (const event of reader) {
-  console.log('Received:', event);
-}
+```bash
+pnpm exec loxtep generate
 ```
 
-The reader yields events as an async iterable. By default it generates a
-reader bot ID of `sdk-reader-{data-product-name}` for checkpoint tracking.
+Pulls live metadata from the platform into `.loxtep/generated/index.ts` (data
+products, connectors, domains, queues, workflows). Re-run after platform changes.
 
-### Reader options
+---
 
-```typescript
-const reader = await client.get_reader('my-data-product', {
-  bot_id: 'my-consumer',     // Custom reader identity for checkpointing
-  from: 'z/2024/01/01',      // Start position (default: latest checkpoint)
-  batch_size: 200,            // Events per batch (default: 100)
-});
+## Step 6: Explore the Platform
+
+```bash
+pnpm exec loxtep data-products list
+pnpm exec loxtep workflows list --project-id <project-id>
+pnpm exec loxtep domains list
 ```
 
+On a new account, **data products may be empty** until you create and deploy
+workflows (CLI, MCP, or Web UI). That's expected — don't call `get_writer` yet.
+
 ---
 
-## Complete Example
+## Step 7: Use the SDK in Application Code
 
-```typescript
-// first-event.ts
-// Run: pnpm exec tsx first-event.ts
+Prefer workspace auto-config instead of hand-building `api_url` and tokens:
 
+```typescript
 import { LoxtepClient } from '@loxtep/sdk';
 
-async function main() {
-  const client = new LoxtepClient({
-    api_url: process.env.LOXTEP_API_URL,
-    auth: { type: 'jwt', token: process.env.LOXTEP_TOKEN },
-  });
+const client = await LoxtepClient.fromWorkspace();
+const { user, organization } = await client.session.get_current_user();
 
-  // Write an event to a data product
-  const writer = await client.get_writer('my-data-product');
-
-  writer.write({
-    id: `event-${Date.now()}`,
-    timestamp: new Date().toISOString(),
-    payload: { message: 'Hello from the Loxtep SDK!' },
-  });
-
-  await writer.close();
-  console.log('✓ Event written');
-
-  // Read it back
-  const reader = await client.get_reader('my-data-product', {
-    bot_id: 'quickstart-reader',
-  });
+console.log(user.email, organization?.name);
+```
 
-  for await (const event of reader) {
-    console.log('✓ Event received:', JSON.stringify(event, null, 2));
-    break; // Just read the first one to verify
-  }
+`fromWorkspace()` reads `.loxtep/project.json` and `./.loxtep/credentials.json`
+(walking up from `cwd`). Env overrides: `LOXTEP_API_URL`, `LOXTEP_TOKEN`,
+`LOXTEP_ORGANIZATION_ID`, `LOXTEP_PROJECT_ID`, `LOXTEP_INSTANCE_ID`.
 
-  console.log('Done!');
-}
+List or manage resources via namespaced APIs:
 
-main().catch(console.error);
+```typescript
+const { items } = await client.build.data_products.list();
+const instances = await client.workspace.instances.list();
 ```
 
 ---
 
-## Troubleshooting
-
-### Data product not found
+## Step 8: Write and Read Events (after deploy)
 
-**Symptom:** `NotFoundError: Data product 'my-data-product' not found`
+`get_writer` and `get_reader` resolve queue, bot, and stream configuration from
+**deployment metadata**. They only work for data products that exist **and** are
+deployed on your attached instance.
 
-**Cause:** The SDK could not find a data product matching the name you provided.
+1. Author a workflow under `workflows/` (see [Code-first CLI](./code-first-cli.md)).
+2. `pnpm exec loxtep deploy`
+3. Confirm the data product name:
 
-**Fix:**
-
-1. Verify the data product name is spelled correctly (names are case-sensitive).
-2. Check that the data product's workflow has been deployed to an instance.
-3. If you're using a UUID, confirm it matches an existing data product ID.
+   ```bash
+   pnpm exec loxtep data-products list
+   ```
 
-```bash
-# List data products in your organization
-pnpm exec loxtep data-products list
-```
+4. Stream from application code:
 
----
+```typescript
+const client = await LoxtepClient.fromWorkspace();
 
-### Data product not deployed
+const writer = await client.get_writer('orders'); // use your deployed name
+writer.write({
+  order_id: 'ord_1',
+  total: 99.5,
+});
+await writer.close();
 
-**Symptom:** `StreamingError: Data product 'my-data-product' is not deployed.
-Deploy the workflow first.`
+const reader = await client.get_reader('orders', {
+  bot_id: 'my-app-reader',
+});
+for await (const event of reader) {
+  console.log(event);
+  break;
+}
+```
 
-**Cause:** The data product exists in the workflow graph but has not been
-deployed to an instance. Runtime bindings (queue name, bot ID) are only
-available after deployment.
+The SDK resolves runtime bindings automatically — no manual queue names or bot IDs.
 
-**Fix:**
+### Writer / reader options
 
-1. Deploy the workflow containing the data product:
+```typescript
+await client.get_writer('orders', {
+  batch_size: 500,
+  max_retries: 5,
+});
 
-```bash
-pnpm exec loxtep deploy <workflow-id>
+await client.get_reader('orders', {
+  bot_id: 'my-consumer',
+  from: undefined, // latest checkpoint
+  batch_size: 200,
+});
 ```
 
-2. Or deploy via the Loxtep UI: **Workflows** → select your workflow → **Deploy**.
-
-3. If using an AI assistant with MCP, use the `deploy_workflow` tool.
-
 ---
 
-### Unable to resolve stream configuration
-
-**Symptom:** `StreamingError: Failed to resolve stream config for instance
-<instance-id>`
+## Troubleshooting
 
-**Cause:** The SDK resolved the data product and its instance, but could not
-retrieve the stream configuration from the instance record.
+### Run `loxtep init` first / not attached
 
-**Fix:**
+**Symptom:** `Run loxtep init first` or `Run loxtep attach`
 
-1. Verify the instance is fully provisioned and running in the Loxtep UI.
-2. Check that your account has `instances:read` permission on the target instance.
-3. If the instance was recently created, wait a few minutes for provisioning to
-   complete.
-4. Contact your platform admin if the instance shows as provisioned but
-   resolution still fails.
+**Fix:** Complete [Step 3](#step-3-scaffold-a-workspace) and
+[Step 4](#step-4-attach-to-an-instance).
 
 ---
 
-### Multiple data products match
-
-**Symptom:** `AmbiguityError: Multiple data products match 'my-data-product'.
-Found matches on instances: [instance-a, instance-b]`
+### Data product not found
 
-**Cause:** The same data product name exists on multiple instances and the SDK
-cannot determine which one you mean.
+**Symptom:** `NotFoundError: Data product 'orders' not found`
 
-**Fix:**
+**Fix:** Deploy a workflow that publishes the data product, then verify with
+`pnpm exec loxtep data-products list`. Names are case-sensitive.
 
-1. Set `instance_id` in the client options to scope resolution to a specific
-   instance:
+---
 
-```typescript
-const client = new LoxtepClient({
-  api_url: process.env.LOXTEP_API_URL,
-  auth: { type: 'jwt', token: process.env.LOXTEP_TOKEN },
-  instance_id: process.env.LOXTEP_INSTANCE_ID,
-});
-```
+### Data product not deployed
 
-2. Or use the data product's UUID instead of its name:
+**Symptom:** `StreamingError: … is not deployed`
 
-```typescript
-const writer = await client.get_writer('09fa202b-...');
-```
+**Fix:** The catalog entry exists but has no runtime bindings yet. Run
+`pnpm exec loxtep deploy` or deploy via MCP/UI, then retry.
 
 ---
 
-### Missing Auth Token
-
-**Symptom:** `AuthenticationError: No authentication token found`
+### Missing auth token
 
-**Cause:** The SDK cannot find a JWT token. Set `LOXTEP_AUTH_TOKEN` (CLI) or
-`LOXTEP_TOKEN` (programmatic auto-config), or run `pnpm exec loxtep login` so
-`./.loxtep/credentials.json` exists (or `~/.loxtep/credentials.json` with
-`--global`).
+**Symptom:** `Missing api_url or access token` / authentication errors
 
 **Fix:**
 
 ```bash
-# Option 1: Log in interactively
 pnpm exec loxtep login
-
-# Option 2: Set the token directly (CLI / manual client bootstrap)
-export LOXTEP_AUTH_TOKEN="your-jwt-token"
-# Auto-config via LoxtepClient.fromWorkspace() also reads LOXTEP_TOKEN
-export LOXTEP_TOKEN="your-jwt-token"
+pnpm exec loxtep whoami
 ```
 
 ---
 
-## Next Steps
+### Multiple data products match
+
+**Symptom:** `AmbiguityError: Multiple data products match …`
+
+**Fix:** Set `instance_id` in `.loxtep/project.json` via `attach`, or pass a
+data product UUID instead of a name.
 
-Now that you've written and read your first event, explore these resources:
+---
+
+## Next Steps
 
 | Resource | Description |
 |----------|-------------|
-| [Code-first CLI guide](./code-first-cli.md) | `loxtep init`, attach, generate, test, deploy |
-| [Quick Reference Card](./quick-reference.md) | Single-page cheat sheet for common SDK operations |
-| [Event Replay Cookbook](./event-replay-cookbook.md) | Patterns for replaying and reprocessing historical events |
-| [MCP → SDK Mapping](./sdk-mcp-mapping.md) | How MCP tools map to SDK methods |
+| [Code-first CLI guide](./code-first-cli.md) | Workflow modules, `test`, `deploy` |
+| [Quick Reference Card](./quick-reference.md) | Cheat sheet for common operations |
+| [Event Replay Cookbook](./event-replay-cookbook.md) | Replay and reprocess historical events |
 
-See the [SDK README](../README.md) for the full API surface.
+See the [SDK README](../README.md) for the full API surface and CLI reference.

package/docs/quick-reference.md

@@ -1,8 +1,8 @@
 # SDK Quick Reference Card
 
-Concise cheat sheet for common Loxtep SDK operations (Node.js **v0.7+** MCP
-facades). For full walkthroughs, see the [Getting Started Guide](./getting-started.md)
-(programmatic) or [Code-first CLI guide](./code-first-cli.md) (`loxtep init`).
+Concise cheat sheet for common Loxtep SDK operations (Node.js).
+For full walkthroughs, see the [Getting Started Guide](./getting-started.md)
+or [Code-first CLI guide](./code-first-cli.md).
 
 ---
 
@@ -13,7 +13,11 @@ facades). For full walkthroughs, see the [Getting Started Guide](./getting-start
 ```typescript
 import { LoxtepClient } from '@loxtep/sdk';
 
-const client = new LoxtepClient({
+// Recommended after `login` + `init` + `attach`:
+const client = await LoxtepClient.fromWorkspace();
+
+// Explicit config (CI, multi-tenant scripts):
+const explicit = new LoxtepClient({
   api_url: process.env.LOXTEP_API_URL,
   auth: { type: 'jwt', token: process.env.LOXTEP_AUTH_TOKEN! },
   organization_id: process.env.LOXTEP_ORGANIZATION_ID,
@@ -21,9 +25,6 @@ const client = new LoxtepClient({
   instance_id: process.env.LOXTEP_INSTANCE_ID,
   region: process.env.LOXTEP_REGION,
 });
-
-// Or from workspace files after `loxtep init` + `loxtep login`:
-const wsClient = LoxtepClient.fromWorkspace();
 ```
 
 ### Python
@@ -51,7 +52,7 @@ bus config from deployment metadata.
 ### Node.js
 
 ```typescript
-const writer = await client.get_writer('my-data-product');
+const writer = await client.get_writer('orders'); // deployed data product name
 
 writer.write({ id: 'evt-1', payload: { key: 'value' } });
 writer.write({ id: 'evt-2', payload: { key: 'value' } });
@@ -175,8 +176,6 @@ const hits = await client.query.catalog.search({ query: 'orders' });
 | **Catalog search** | `client.query.catalog.search({ query })` |
 | **Invalidate cache** | `client.build.data_products.invalidate_cache('name')` |
 
-See [MCP → SDK mapping](./sdk-mcp-mapping.md) for all 10 facades.
-
 ---
 
 ## CLI Shortcuts
@@ -220,4 +219,4 @@ in application code.
 |----------|-------------|
 | [Getting Started Guide](./getting-started.md) | Zero-to-first-event walkthrough |
 | [Event Replay Cookbook](./event-replay-cookbook.md) | Replay patterns (`build.data_products`, `observe`) |
-| [MCP → SDK Mapping](./sdk-mcp-mapping.md) | How MCP tools map to SDK methods |
+| [Code-first CLI guide](./code-first-cli.md) | `loxtep init` through deploy |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@loxtep/sdk",
-  "version": "0.7.7",
+  "version": "0.7.10",
   "description": "Loxtep SDK for Node.js — the Enterprise Context Layer: data products, workflows, projects, queues, and machine-usable context for AI",
   "author": "Loxtep <engineering@loxtep.io>",
   "homepage": "https://loxtep.io",

package/dist/cli/commands/connections-cmd.d.ts

@@ -1,19 +0,0 @@
-/**
- * CLI: loxtep connections list | connections get <id> | connections create ... | connections test <id>
- */
-export interface ConnectionsCmdOptions {
-    configFilePath?: string;
-    credentialsPath?: string;
-    customerMcpPath?: string;
-}
-export declare function runConnectionsList(options?: ConnectionsCmdOptions): Promise<void>;
-export declare function runConnectionsGet(connectionId: string, options?: ConnectionsCmdOptions): Promise<void>;
-export declare function runConnectionsCreate(params: {
-    name?: string;
-    type?: string;
-    key?: string;
-    data?: string;
-    configuration?: Record<string, unknown>;
-}, options?: ConnectionsCmdOptions): Promise<void>;
-export declare function runConnectionsTest(connectionId: string, options?: ConnectionsCmdOptions): Promise<void>;
-//# sourceMappingURL=connections-cmd.d.ts.map

package/dist/cli/commands/connections-cmd.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"connections-cmd.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/connections-cmd.ts"],"names":[],"mappings":"AAAA;;GAEG;AAIH,MAAM,WAAW,qBAAqB;IACpC,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB,eAAe,CAAC,EAAE,MAAM,CAAC;IACzB,eAAe,CAAC,EAAE,MAAM,CAAC;CAC1B;AAED,wBAAsB,kBAAkB,CAAC,OAAO,GAAE,qBAA0B,GAAG,OAAO,CAAC,IAAI,CAAC,CAI3F;AAED,wBAAsB,iBAAiB,CACrC,YAAY,EAAE,MAAM,EACpB,OAAO,GAAE,qBAA0B,GAClC,OAAO,CAAC,IAAI,CAAC,CAIf;AAED,wBAAsB,oBAAoB,CACxC,MAAM,EAAE;IACN,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,aAAa,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;CACzC,EACD,OAAO,GAAE,qBAA0B,GAClC,OAAO,CAAC,IAAI,CAAC,CAkBf;AAED,wBAAsB,kBAAkB,CACtC,YAAY,EAAE,MAAM,EACpB,OAAO,GAAE,qBAA0B,GAClC,OAAO,CAAC,IAAI,CAAC,CAIf"}

package/dist/cli/commands/connections-cmd.js

@@ -1,39 +0,0 @@
-/**
- * CLI: loxtep connections list | connections get <id> | connections create ... | connections test <id>
- */
-import { requireCliClient } from '../create-cli-client.js';
-export async function runConnectionsList(options = {}) {
-    const { client } = await requireCliClient(options);
-    const result = await client.connections.list({ page_size: 50 });
-    console.log(JSON.stringify(result, null, 2));
-}
-export async function runConnectionsGet(connectionId, options = {}) {
-    const { client } = await requireCliClient(options);
-    const conn = await client.connections.get(connectionId);
-    console.log(JSON.stringify(conn, null, 2));
-}
-export async function runConnectionsCreate(params, options = {}) {
-    const { client } = await requireCliClient(options);
-    const name = params.name ?? '';
-    const type = params.type ?? 'api';
-    const key = params.key ?? params.name ?? '';
-    if (!name || !key) {
-        console.error('Missing required: --name, --type, --key');
-        process.exitCode = 1;
-        return;
-    }
-    const conn = await client.connections.create({
-        name,
-        type: type,
-        key,
-        data: params.data ?? '{}',
-        configuration: params.configuration,
-    });
-    console.log(JSON.stringify(conn, null, 2));
-}
-export async function runConnectionsTest(connectionId, options = {}) {
-    const { client } = await requireCliClient(options);
-    const result = await client.connections.test(connectionId);
-    console.log(JSON.stringify(result, null, 2));
-}
-//# sourceMappingURL=connections-cmd.js.map

package/dist/cli/commands/connections-cmd.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"connections-cmd.js","sourceRoot":"","sources":["../../../src/cli/commands/connections-cmd.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,EAAE,gBAAgB,EAAE,MAAM,yBAAyB,CAAC;AAQ3D,MAAM,CAAC,KAAK,UAAU,kBAAkB,CAAC,UAAiC,EAAE;IAC1E,MAAM,EAAE,MAAM,EAAE,GAAG,MAAM,gBAAgB,CAAC,OAAO,CAAC,CAAC;IACnD,MAAM,MAAM,GAAG,MAAM,MAAM,CAAC,WAAW,CAAC,IAAI,CAAC,EAAE,SAAS,EAAE,EAAE,EAAE,CAAC,CAAC;IAChE,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,SAAS,CAAC,MAAM,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC,CAAC;AAC/C,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,iBAAiB,CACrC,YAAoB,EACpB,UAAiC,EAAE;IAEnC,MAAM,EAAE,MAAM,EAAE,GAAG,MAAM,gBAAgB,CAAC,OAAO,CAAC,CAAC;IACnD,MAAM,IAAI,GAAG,MAAM,MAAM,CAAC,WAAW,CAAC,GAAG,CAAC,YAAY,CAAC,CAAC;IACxD,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,SAAS,CAAC,IAAI,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC,CAAC;AAC7C,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,oBAAoB,CACxC,MAMC,EACD,UAAiC,EAAE;IAEnC,MAAM,EAAE,MAAM,EAAE,GAAG,MAAM,gBAAgB,CAAC,OAAO,CAAC,CAAC;IACnD,MAAM,IAAI,GAAG,MAAM,CAAC,IAAI,IAAI,EAAE,CAAC;IAC/B,MAAM,IAAI,GAAG,MAAM,CAAC,IAAI,IAAI,KAAK,CAAC;IAClC,MAAM,GAAG,GAAG,MAAM,CAAC,GAAG,IAAI,MAAM,CAAC,IAAI,IAAI,EAAE,CAAC;IAC5C,IAAI,CAAC,IAAI,IAAI,CAAC,GAAG,EAAE,CAAC;QAClB,OAAO,CAAC,KAAK,CAAC,yCAAyC,CAAC,CAAC;QACzD,OAAO,CAAC,QAAQ,GAAG,CAAC,CAAC;QACrB,OAAO;IACT,CAAC;IACD,MAAM,IAAI,GAAG,MAAM,MAAM,CAAC,WAAW,CAAC,MAAM,CAAC;QAC3C,IAAI;QACJ,IAAI,EAAE,IAA+C;QACrD,GAAG;QACH,IAAI,EAAE,MAAM,CAAC,IAAI,IAAI,IAAI;QACzB,aAAa,EAAE,MAAM,CAAC,aAAa;KACpC,CAAC,CAAC;IACH,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,SAAS,CAAC,IAAI,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC,CAAC;AAC7C,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,kBAAkB,CACtC,YAAoB,EACpB,UAAiC,EAAE;IAEnC,MAAM,EAAE,MAAM,EAAE,GAAG,MAAM,gBAAgB,CAAC,OAAO,CAAC,CAAC;IACnD,MAAM,MAAM,GAAG,MAAM,MAAM,CAAC,WAAW,CAAC,IAAI,CAAC,YAAY,CAAC,CAAC;IAC3D,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,SAAS,CAAC,MAAM,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC,CAAC;AAC/C,CAAC"}

package/dist/cli/commands/data-assets-cmd.d.ts

@@ -1,12 +0,0 @@
-/**
- * CLI: loxtep data-assets list | data-assets get <id>
- */
-export interface DataAssetsCmdOptions {
-    configFilePath?: string;
-    credentialsPath?: string;
-}
-export declare function runDataAssetsList(options?: DataAssetsCmdOptions): Promise<void>;
-export declare function runDataAssetsGet(dataAssetId: string, options?: DataAssetsCmdOptions): Promise<void>;
-export declare function runDataAssetsQuery(dataAssetId: string, sql: string, options?: DataAssetsCmdOptions): Promise<void>;
-export declare function runDataAssetsTables(dataAssetId: string, options?: DataAssetsCmdOptions): Promise<void>;
-//# sourceMappingURL=data-assets-cmd.d.ts.map

package/dist/cli/commands/data-assets-cmd.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"data-assets-cmd.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/data-assets-cmd.ts"],"names":[],"mappings":"AAAA;;GAEG;AAMH,MAAM,WAAW,oBAAoB;IACnC,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB,eAAe,CAAC,EAAE,MAAM,CAAC;CAC1B;AAED,wBAAsB,iBAAiB,CAAC,OAAO,GAAE,oBAAyB,GAAG,OAAO,CAAC,IAAI,CAAC,CAkBzF;AAED,wBAAsB,gBAAgB,CACpC,WAAW,EAAE,MAAM,EACnB,OAAO,GAAE,oBAAyB,GACjC,OAAO,CAAC,IAAI,CAAC,CAkBf;AAED,wBAAsB,kBAAkB,CACtC,WAAW,EAAE,MAAM,EACnB,GAAG,EAAE,MAAM,EACX,OAAO,GAAE,oBAAyB,GACjC,OAAO,CAAC,IAAI,CAAC,CAkBf;AAED,wBAAsB,mBAAmB,CACvC,WAAW,EAAE,MAAM,EACnB,OAAO,GAAE,oBAAyB,GACjC,OAAO,CAAC,IAAI,CAAC,CAkBf"}