@grepr/cli 1.10.1 → 1.10.2-9020f37

package/build/dist/docs-index/643e906d-e70c-484d-bf4a-1b8eee9f1267.txt

@@ -1,190 +0,0 @@
-Learn how to use infrastructure as code (IaC) to manage your Grepr pipelines with the Grepr Terraform provider.
-
-# Manage Grepr pipelines with Terraform
-
-You can use the Grepr Terraform provider to manage Grepr pipelines using infrastructure as code (IaC) principles. With the Grepr Terraform provider, you can define, deploy, and manage your pipelines in a consistent and repeatable manner.
-
-## Requirements \[#tf-provider-reqs]
-
-To use the Grepr Terraform provider, you must have:
-
-* Terraform or OpenTofu CLI version 1.0 or later.
-* OAuth2 client credentials for authentication. To obtain the required credentials, create a service account in the Grepr UI. See [Manage Grepr service accounts](/admin/service-accounts).
-
-## Install the Grepr provider
-
-The Grepr provider is published to the [OpenTofu registry](https://search.opentofu.org/provider/grepr/grepr/). To install it, declare it in the `required_providers` block of your configuration. To use the OpenTofu CLI, use the following configuration:
-
-```hcl
-terraform {
-  required_providers {
-    grepr = {
-      source  = "grepr/grepr"
-      version = "~> 1.0"
-    }
-  }
-}
-```
-
-To use the Terraform CLI, you must use the fully qualified source address `registry.opentofu.org/grepr/grepr`:
-
-```hcl
-terraform {
-  required_providers {
-    grepr = {
-      source  = "registry.opentofu.org/grepr/grepr"
-      version = "~> 1.0"
-    }
-  }
-}
-```
-
-Then initialize your working directory to download the provider:
-
-```bash
-terraform init # Or tofu init
-```
-
-## Configure authentication for the Grepr Terraform provider
-
-To configure the required OAuth2 credentials for authentication, add a provider block to your Terraform configuration with the `host`, `client_id`, and `client_secret` fields:
-
-```hcl
-provider "grepr" {
-  host          = "https://<your-org>.app.grepr.ai"
-  client_id     = var.<grepr-client-id>
-  client_secret = var.<grepr-client-secret>
-}
-```
-
-Replace:
-
-* `<your-org>` with your organization name.
-* `<grepr-client-id>` with your service account client ID.
-* `<grepr-client-secret>` with your service account client secret.
-
-Alternatively, you can use environment variables to set the required credentials. The provider automatically reads these environment variables if you set them:
-
-```bash
-export GREPR_HOST=https://<your-org>.app.grepr.ai
-export GREPR_CLIENT_ID=<your-client-id>
-export GREPR_CLIENT_SECRET=<your-client-secret>
-```
-
-## Import an existing pipeline
-
-To bring an existing pipeline under Terraform management, use the `terraform import` command with the pipeline's ID or name:
-
-```bash
-terraform import grepr_pipeline.example <pipeline-id-or-name>
-```
-
-To automatically import an existing pipeline without using the `import` command, create a `grepr_pipeline` resource with the same name as the existing pipeline. The provider will detect and import the existing pipeline.
-
-## Example: create a pipeline
-
-The following example shows a simple pipeline that uses a Datadog log agent source, a Grok parser, and an Iceberg table sink. To improve maintainability and avoid conflicts with Terraform reserved symbols or keywords, Grepr recommends defining your pipeline's job graph in a separate JSON file. You then reference this JSON file in your Terraform configuration. This example demonstrates how to define a pipeline job graph in a JSON file and reference the file in the Terraform configuration.
-
-A common development workflow is to create a pipeline in the Grepr UI or API, test it and make changes until it meets your requirements, then copy the generated JSON to a file for use with your Terraform configuration. If you choose to create pipelines through the API, see [Create and manage jobs with the Grepr REST APIs](/apis/job-creation-guide).
-
-After you've completed development of your pipeline, to find its JSON definition in the UI, click **Jobs** in the menu bar, click the three-dot menu in the **Actions** column for your pipeline, and click **Edit JSON** to view and copy the JSON. Save the copied JSON to a file in your Terraform project, for example, `pipeline.json`:
-
-```json
-{
-  "vertices": [
-    {
-      "type": "datadog-log-agent-source",
-      "name": "source",
-      "integrationId": "<your-integration-id>"
-    },
-    {
-      "type": "grok-parser",
-      "name": "parser",
-      "grokParsingRules": [
-        "%{TIMESTAMP_ISO8601:timestamp} %{LOGLEVEL:level} %{GREEDYDATA:message}"
-      ]
-    },
-    {
-      "type": "logs-iceberg-table-sink",
-      "name": "sink",
-      "datasetId": "<your-dataset-id>"
-    }
-  ],
-  "edges": ["source -> parser", "parser -> sink"]
-}
-```
-
-`<your-integration-id>` and `<your-dataset-id>` are the identifiers of the Datadog integration and dataset used by this pipeline. If you copied the JSON from an existing pipeline, these fields are already set to the correct value.
-
-Then reference the JSON file in your Terraform configuration:
-
-```hcl
-resource "grepr_pipeline" "example" {
-  name           = "my_pipeline"
-  job_graph_json = file("${path.module}/pipeline.json")
-  desired_state  = "RUNNING"
-}
-```
-
-Use `terraform init` to download the provider, `terraform plan` to preview your changes, and `terraform apply` to apply the configuration and create the pipeline. With the OpenTofu CLI, use the equivalent `tofu` commands:
-
-```bash
-terraform init
-terraform plan
-terraform apply
-```
-
-You can also define the job graph directly in the Terraform configuration using `jsonencode`:
-
-```hcl
-resource "grepr_pipeline" "example" {
-  name = "my_pipeline"
-
-  job_graph_json = jsonencode({
-    vertices = [
-      {
-        type          = "datadog-log-agent-source"
-        name          = "source"
-        integrationId = var.datadog_integration_id
-      },
-      {
-        type = "grok-parser"
-        name = "parser"
-        grokParsingRules = ["%{TIMESTAMP_ISO8601:timestamp} %{LOGLEVEL:level} %{GREEDYDATA:message}"]
-      },
-      {
-        type      = "logs-iceberg-table-sink"
-        name      = "sink"
-        datasetId = var.dataset_id
-      }
-    ]
-    edges = ["source -> parser", "parser -> sink"]
-  })
-}
-```
-
-## Resource attributes
-
-The `grepr_pipeline` resource supports these attributes:
-
-| Attribute | Type | Required | Description |
-| --- | --- | --- | --- |
-| `name` | String | Yes | The pipeline name. Must be lowercase alphanumeric with underscores, 1-128 characters. |
-| `job_graph_json` | String | Yes | The job graph as a JSON string. Use `file()` to load from a JSON file or `jsonencode` to define inline. |
-| `desired_state` | String | No | The desired state: `RUNNING` or `STOPPED`. Defaults to `RUNNING`. |
-| `team_ids` | Set of Strings | No | Team IDs to associate with this pipeline. |
-| `tags` | Map of Strings | No | Custom tags for the pipeline. |
-| `wait_for_state` | Boolean | No | Wait for the pipeline to reach the desired state. Defaults to `true`. |
-| `state_timeout` | Number | No | Timeout in seconds for state transitions. Defaults to `600`. |
-| `rollback_enabled` | Boolean | No | Enable automatic rollback on update failures. Defaults to `false`. |
-
-### Read-only attributes
-
-| Attribute | Type | Description |
-| --- | --- | --- |
-| `id` | String | The unique identifier of the pipeline. |
-| `version` | Number | The current version of the pipeline. Increments on updates. |
-| `state` | String | The actual current state of the pipeline. |
-| `organization_id` | String | The organization ID that owns this pipeline. |
-| `created_at` | String | The timestamp when the pipeline was created. |
-| `updated_at` | String | The timestamp when the pipeline was last updated. |

package/build/dist/docs-index/6827ee3f-b2e2-480d-8deb-fd8a4deab721.txt

@@ -1,24 +0,0 @@
-# Delete a SumoLogic integration
-
-**DELETE** `/v1/integrations/sumo/{id}`
-
-**Operation ID**: `delete_16`
-**Summary**: Delete a SumoLogic integration
-Deletes an integration to connect to SumoLogic. This will delete the associated keys as well. No-op if already deleted.
-
-## Tags
-- Sumo Logic Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Responses
-
-### 204
-
-Integration deleted successfully
-
-### 401
-
-Unauthorized

package/build/dist/docs-index/6d6de590-bb42-464a-96aa-3ac84bea39d8.txt

@@ -1,29 +0,0 @@
-# Get a GitHub MCP integration
-
-**GET** `/v1/integrations/github-mcp/{id}`
-
-**Operation ID**: `get_9`
-**Summary**: Get a GitHub MCP integration
-Get a GitHub MCP integration by ID.
-
-## Tags
-- GitHub MCP Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Responses
-
-### 200
-
-Integration retrieved successfully
-
-- **Content-Type**: `application/json` / `ReadGithubMcp`
-### 401
-
-Unauthorized
-
-### 404
-
-Integration not found.

package/build/dist/docs-index/6f8ac982-128f-4619-801b-3e20006ed0f2.txt

@@ -1,20 +0,0 @@
-# List all Datadog MCP integrations
-
-**GET** `/v1/integrations/datadog-mcp`
-
-**Operation ID**: `list_8`
-**Summary**: List all Datadog MCP integrations
-Get all Datadog MCP server integrations for your organization. This will contain masked API keys if present.
-
-## Tags
-- Datadog MCP Integration
-## Responses
-
-### 200
-
-Integrations retrieved successfully
-
-- **Content-Type**: `application/json` / `ItemsCollectionReadDatadogMcp`
-### 401
-
-Unauthorized

package/build/dist/docs-index/709cec8b-2ba8-4755-bb58-3b75e431346b.txt

@@ -1,29 +0,0 @@
-# Get a Gemini integration
-
-**GET** `/v1/integrations/gemini/{id}`
-
-**Operation ID**: `get_7`
-**Summary**: Get a Gemini integration
-Get a Gemini integration by ID.
-
-## Tags
-- Gemini Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Responses
-
-### 200
-
-Integration retrieved successfully
-
-- **Content-Type**: `application/json` / `ReadGemini`
-### 401
-
-Unauthorized
-
-### 404
-
-Integration not found.

package/build/dist/docs-index/793b4120-a45b-4e7f-b2d0-e6bcbe9a4beb.txt

@@ -1,34 +0,0 @@
-# Create a S3 Data Warehouse integration
-
-**POST** `/v1/integrations/s3-data-warehouse`
-
-**Operation ID**: `create_5`
-**Summary**: Create a S3 Data Warehouse integration
-Creates an external S3 Data Warehouse integration
-
-## Tags
-- External S3 Data Warehouse Integration
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `WriteS3DataWarehouse`
-
-## Responses
-
-### 201
-
-S3 Data Warehouse integration created successfully
-
-- **Content-Type**: `application/json` / `ReadS3DataWarehouse`
-### 400
-
-Bucket is not accessible or the role is invalid
-
-### 401
-
-Unauthorized
-
-### 409
-
-S3 Data Warehouse integration already exists

package/build/dist/docs-index/7a4f351a-5b44-4f77-98e4-98739ba47e31.txt

@@ -1,32 +0,0 @@
-# Create a GitHub MCP integration
-
-**POST** `/v1/integrations/github-mcp`
-
-**Operation ID**: `create_8`
-**Summary**: Create a GitHub MCP integration
-Creates an integration to connect to a GitHub MCP server.
-
-## Tags
-- GitHub MCP Integration
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `WriteGithubMcp`
-
-## Responses
-
-### 200
-
-Integration created successfully
-
-- **Content-Type**: `application/json` / `ReadGithubMcp`
-### 401
-
-Unauthorized
-
-### 409
-
-Integration already exists.
-
-- **Content-Type**: `application/json` / `ReadGithubMcp`

package/build/dist/docs-index/7dadb2bb-1aa9-466d-88df-d2d82e12207a.txt

@@ -1,29 +0,0 @@
-# Get a Datadog integration
-
-**GET** `/v1/integrations/datadog/{id}`
-
-**Operation ID**: `get_4`
-**Summary**: Get a Datadog integration
-Get an integration to connect to Datadog.
-
-## Tags
-- Datadog Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Responses
-
-### 200
-
-Integration retrieved successfully
-
-- **Content-Type**: `application/json` / `ReadDatadog`
-### 401
-
-Unauthorized
-
-### 404
-
-Integration not found.

package/build/dist/docs-index/88a5e660-4f69-4df0-9f83-bc3acf44cf3c.txt

@@ -1,39 +0,0 @@
-# Update a SumoLogic integration.
-
-**PUT** `/v1/integrations/sumo/{id}`
-
-**Operation ID**: `update_15`
-**Summary**: Update a SumoLogic integration.
-Updates an integration to connect to SumoLogic. The version should be increased by one for every new update in order for the write to succeed. Otherwise, a '409 Conflict' will be returned.
-
-## Tags
-- Sumo Logic Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `WriteSumo`
-
-## Responses
-
-### 200
-
-Integration updated successfully
-
-- **Content-Type**: `application/json` / `ReadSumo`
-### 401
-
-Unauthorized
-
-### 404
-
-Integration not found.
-
-### 409
-
-Integration was modified or deleted concurrently.

package/build/dist/docs-index/8bfadd48-9489-4bb8-b302-f42920cfc7dd.txt

@@ -1,32 +0,0 @@
-# Create a SumoLogic integration
-
-**POST** `/v1/integrations/sumo`
-
-**Operation ID**: `create_16`
-**Summary**: Create a SumoLogic integration
-Creates an integration to connect to SumoLogic.
-
-## Tags
-- Sumo Logic Integration
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `WriteSumo`
-
-## Responses
-
-### 200
-
-Integration created successfully
-
-- **Content-Type**: `application/json` / `ReadSumo`
-### 401
-
-Unauthorized
-
-### 409
-
-Integration already exists.
-
-- **Content-Type**: `application/json` / `ReadSumo`

package/build/dist/docs-index/9315f153-c4b0-4e50-9797-cc2d7cea87a6.txt

@@ -1,29 +0,0 @@
-# Get a Datadog MCP integration
-
-**GET** `/v1/integrations/datadog-mcp/{id}`
-
-**Operation ID**: `get_8`
-**Summary**: Get a Datadog MCP integration
-Get a Datadog MCP integration by ID.
-
-## Tags
-- Datadog MCP Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Responses
-
-### 200
-
-Integration retrieved successfully
-
-- **Content-Type**: `application/json` / `ReadDatadogMcp`
-### 401
-
-Unauthorized
-
-### 404
-
-Integration not found.

package/build/dist/docs-index/959b72fb-f0fc-4bfa-b08f-b3bd36f2747e.txt

@@ -1,39 +0,0 @@
-# Update a webhook integration
-
-**PUT** `/v1/integrations/webhooks/{id}`
-
-**Operation ID**: `update_16`
-**Summary**: Update a webhook integration
-Updates a webhook integration. The version should be increased by one for every new update in order for the write to succeed. Otherwise, a '409 Conflict' will be returned.
-
-## Tags
-- Webhook Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `WriteWebhookIntegration`
-
-## Responses
-
-### 200
-
-Integration updated successfully
-
-- **Content-Type**: `application/json` / `ReadWebhookIntegration`
-### 401
-
-Unauthorized
-
-### 404
-
-Integration not found.
-
-### 409
-
-Integration was modified or deleted concurrently.

package/build/dist/docs-index/95b41157-d2be-40f8-8318-c1751be3e3c7.txt

@@ -1,32 +0,0 @@
-# Create a Slack MCP integration
-
-**POST** `/v1/integrations/slack-mcp`
-
-**Operation ID**: `create_10`
-**Summary**: Create a Slack MCP integration
-Creates an integration to connect to a Slack MCP server.
-
-## Tags
-- Slack MCP Integration
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `WriteSlackMcp`
-
-## Responses
-
-### 200
-
-Integration created successfully
-
-- **Content-Type**: `application/json` / `ReadSlackMcp`
-### 401
-
-Unauthorized
-
-### 409
-
-Integration already exists.
-
-- **Content-Type**: `application/json` / `ReadSlackMcp`

package/build/dist/docs-index/9e0a2968-77b6-43ed-95bf-952591023aad.txt

@@ -1,29 +0,0 @@
-# Get a NewRelic integration
-
-**GET** `/v1/integrations/newrelic/{id}`
-
-**Operation ID**: `get_12`
-**Summary**: Get a NewRelic integration
-Get an integration to connect to NewRelic.
-
-## Tags
-- New Relic Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Responses
-
-### 200
-
-Integration retrieved successfully
-
-- **Content-Type**: `application/json` / `ReadNewRelic`
-### 401
-
-Unauthorized
-
-### 404
-
-Integration not found.

package/build/dist/docs-index/9ebbbed2-1a8b-415c-9aec-508199180c77.txt

@@ -1,26 +0,0 @@
-# TranscriptMessage
-
-**Type**: `object`
-
-## Properties
-
-- name: id (optional)
-  type: string
-
-- name: role (optional)
-  type: enum: `SYSTEM`, `TRIGGER_SIGNAL`, `USER`, `ASSISTANT`, `TOOL_RESULT`
-
-- name: text (optional)
-  type: string
-
-- name: timestamp (optional)
-  type: string
-
-- name: toolCallId (optional)
-  type: string
-
-- name: toolCalls (optional)
-  type: array of `TranscriptToolCall`
-
-- name: toolName (optional)
-  type: string

package/build/dist/docs-index/a93bfd94-2e27-4173-a696-73a1fd267d8a.txt

@@ -1,35 +0,0 @@
-# Update an S3 Vector Index integration
-
-**PUT** `/v1/integrations/s3-vector-index/{id}`
-
-**Operation ID**: `update_13`
-**Summary**: Update an S3 Vector Index integration
-Updates an existing S3 Vector Index integration. Note: dimensions and distanceMetric are immutable after creation.
-
-## Tags
-- S3 Vector Index Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `WriteS3VectorIndex`
-
-## Responses
-
-### 200
-
-S3 Vector Index integration updated successfully
-
-- **Content-Type**: `application/json` / `ReadS3VectorIndex`
-### 401
-
-Unauthorized
-
-### 404
-
-S3 Vector Index integration not found

package/build/dist/docs-index/ab22c6e8-d203-4a9a-b0f8-7314bf16b833.txt

@@ -1,29 +0,0 @@
-# Get a S3 Data Warehouse integration
-
-**GET** `/v1/integrations/s3-data-warehouse/{id}`
-
-**Operation ID**: `get_6`
-**Summary**: Get a S3 Data Warehouse integration
-Gets an external S3 Data Warehouse integration
-
-## Tags
-- External S3 Data Warehouse Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Responses
-
-### 200
-
-S3 Data Warehouse integration retrieved successfully
-
-- **Content-Type**: `application/json` / `ReadS3DataWarehouse`
-### 401
-
-Unauthorized
-
-### 404
-
-S3 Data Warehouse integration not found