@grepr/cli 1.12.7 → 1.14.3-5fb972a

package/build/dist/docs-index/d5c6ec91-1148-43d3-9e65-a34737d2ffed.txt

@@ -1,40 +0,0 @@
-# List an issue's history
-
-**GET** `/v1/issues/{idOrNumber}/events`
-
-**Operation ID**: `events`
-**Summary**: List an issue's history
-Returns an issue's history entries, newest first. Repeat kind to return only those kinds, for example to leave out OCCURRED sightings.
-
-## Tags
-- Issues
-## Parameters
-
-- **idOrNumber** (required) - path
-  - Type: string
-- **cursor** (optional) - query
-  - Type: string
-- **limit** (optional) - query
-  - Type: integer
-- **kind** (optional) - query
-  - Type: array of enum: `CREATED`, `UPDATED`, `TRANSITIONED`, `LOCKS_CHANGED`, `COMMENTED`, `GUIDANCE_CHANGED`, `COMMENT_EDITED`, `COMMENT_DELETED`, `ASSIGNMENT_CHANGED`, `OCCURRED`, `HANDED_OFF`, `RUN_NOT_STARTED`
-
-## Responses
-
-### 200
-
-History retrieved
-
-- **Content-Type**: `application/json` / `IssueEventsPage`
-### 400
-
-Malformed cursor, or one issued for other kinds
-
-- **Content-Type**: `application/json` / `IssueErrorResponse`
-### 401
-
-Unauthorized
-
-### 404
-
-Issue not found

package/build/dist/docs-index/d655d526-3216-4882-9b70-1bcb2ad3e7b2.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/d655d526-3216-4882-9b70-1bcb2ad3e7b2.txt

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

package/build/dist/docs-index/d725105d-c73d-4f62-b409-05113cdd7c70.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/d725105d-c73d-4f62-b409-05113cdd7c70.txt

@@ -1,43 +0,0 @@
-# LogsIcebergTableSource
-
-**Type**: `object`
-
-## Properties
-
-- name: datasetId (required)
-  type: string
-  description: The ID of the dataset to read data from.
-
-- name: end (required)
-  type: string
-  description: End of time interval to query data for.
-
-- name: limit (optional)
-  type: integer
-  description: The maximum number of rows to process
-
-- name: name (required)
-  type: string
-
-- name: offset (optional)
-  type: integer
-  description: Offset on the number of rows to process
-
-- name: query (required)
-  type: `query`
-
-- name: sortOrder (optional)
-  type: enum: `ASCENDING`, `DESCENDING`, `UNSORTED`
-  description: The order in which the rows should be sorted by
-
-- name: start (required)
-  type: string
-  description: Start of time interval to query data for.
-
-- name: type (required)
-  type: enum: `logs-iceberg-table-source`
-  description: Reads events from an Iceberg table for processing.
-
-- name: variables (optional)
-  type: object
-  description: Variables that can be used to modify the query while parsed

package/build/dist/docs-index/d784cebe-4cb7-48f4-9c20-3ef899028aa2.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/d784cebe-4cb7-48f4-9c20-3ef899028aa2.txt

@@ -1,29 +0,0 @@
-# Get the issues an agent reads and works on
-
-**GET** `/v1/agents/{id}/issue-reach`
-
-**Operation ID**: `issueReach`
-**Summary**: Get the issues an agent reads and works on
-Returns whose issues the agent reads, and whose it can be handed, pick up and change: every issue in your organization or those of some teams, from its service account's issue scopes.
-
-## Tags
-- Agents
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Responses
-
-### 200
-
-Issue reach retrieved successfully
-
-- **Content-Type**: `application/json` / `AgentIssueScopes`
-### 401
-
-Unauthorized
-
-### 404
-
-Agent not found

package/build/dist/docs-index/d7df2717-4487-4598-8629-c1c98ca2a9a8.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/d7df2717-4487-4598-8629-c1c98ca2a9a8.txt

@@ -1,17 +0,0 @@
-# TagNode
-
-**Type**: `object`
-
-## Properties
-
-- name: tagKey (required)
-  type: string
-  description: The tag key 
-
-- name: tagValue (required)
-  type: string
-  description: This is a string that is matched against the tag value.
-
-- name: type (required)
-  type: enum: `tag-node`
-  description: A node that represents a tag key and value in a parsed query.

package/build/dist/docs-index/d7e7cf30-f2b0-4f33-925f-4d0c16b83cab.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/d7e7cf30-f2b0-4f33-925f-4d0c16b83cab.txt

@@ -1,11 +0,0 @@
-# AgentRecentHealth
-
-**Type**: `object`
-
-## Properties
-
-- name: completed (optional)
-  type: integer
-
-- name: failed (optional)
-  type: integer

package/build/dist/docs-index/d801c0f9-f530-4cbd-8a03-815383b15605.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/d801c0f9-f530-4cbd-8a03-815383b15605.txt

@@ -1,29 +0,0 @@
-# Get a S3 Data Warehouse integration
-
-**GET** `/v1/integrations/s3-data-warehouse/{id}`
-
-**Operation ID**: `getS3DataWarehouseIntegration`
-**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

package/build/dist/docs-index/d81d3091-92b3-4602-ad00-d5f2c7522094.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/d81d3091-92b3-4602-ad00-d5f2c7522094.txt

@@ -1,20 +0,0 @@
-# OtlpTraceAgentSource
-
-**Type**: `object`
-
-## Properties
-
-- name: integrationId (required)
-  type: string
-  description: The integration id for the observability vendor.
-
-- name: name (required)
-  type: string
-
-- name: offsetResetStrategy (optional)
-  type: enum: `EARLIEST`, `LATEST`, `NONE`
-  description: Strategy for resetting Kafka consumer offset when no committed offset exists or has expired. EARLIEST reads from oldest available offset (prevents data loss on restart after retention period). LATEST skips to newest offset (current behavior).
-
-- name: type (required)
-  type: enum: `otlp-trace-agent-source`
-  description: Reads trace events from an OpenTelemetry collector. This is used to process traces from OTLP trace ingestion.

package/build/dist/docs-index/d8719293-f3ee-4d5c-8896-43669ce3acf5.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/d8719293-f3ee-4d5c-8896-43669ce3acf5.txt

@@ -1,32 +0,0 @@
-# Create a NewRelic integration
-
-**POST** `/v1/integrations/newrelic`
-
-**Operation ID**: `createNewRelicIntegration`
-**Summary**: Create a NewRelic integration
-Creates an integration to connect to NewRelic.
-
-## Tags
-- New Relic Integration
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `WriteNewRelic`
-
-## Responses
-
-### 200
-
-Integration created successfully
-
-- **Content-Type**: `application/json` / `ReadNewRelic`
-### 401
-
-Unauthorized
-
-### 409
-
-Integration already exists.
-
-- **Content-Type**: `application/json` / `ReadNewRelic`

package/build/dist/docs-index/d8778c35-3f15-4fa1-8aa6-66b886f018d2.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/d8778c35-3f15-4fa1-8aa6-66b886f018d2.txt

@@ -1,16 +0,0 @@
-# PatternLookupIcebergTableSink
-
-**Type**: `object`
-
-## Properties
-
-- name: datasetId (required)
-  type: string
-  description: The id of the dataset to write to
-
-- name: name (required)
-  type: string
-
-- name: type (required)
-  type: enum: `pattern-lookup-iceberg-table-sink`
-  description: Writes event id to pattern id mappings to an Iceberg Table.

package/build/dist/docs-index/d8d869ef-3090-468f-8ee7-511855ca065c.json

@@ -1 +0,0 @@
-{"docType":"doc"}

package/build/dist/docs-index/d8d869ef-3090-468f-8ee7-511855ca065c.txt

@@ -1,231 +0,0 @@
-Learn how to create a Grepr pipeline, integrate the pipeline with your observability platform, such as Datadog, Splunk, or New Relic, and use that pipeline to lower your observability costs by dynamically reducing shipped log volumes.
-
-# Tutorial: Build your first Grepr pipeline
-
-This tutorial is an end-to-end example that shows you how Grepr dynamically reduces the volume of shipped logs without losing data. It does this by walking you through an example that integrates Grepr with Datadog, creates a Grepr pipeline that processes log events forwarded from Datadog agents, and sends the resulting events to Datadog.
-
-In this tutorial, you:
-
-1. Verify that you can directly send log events from your local environment to Datadog.
-2. Configure a Grepr integration with Datadog.
-3. Configure a Grepr storage integration to store raw logs in the Grepr data lake.
-4. Create a Grepr pipeline that processes raw logs and sends the resulting processed events to Datadog.
-5. Use Docker to simulate multiple hosts sending log events to Grepr by running multiple Datadog agents in your local environment.
-6. Run the pipeline and view the output in the Grepr and Datadog UIs.
-
-> * This tutorial uses Datadog as the observability tool. However, you can use this tutorial to create a pipeline that integrates with any Grepr-supported observability tool. For the complete list of supported observability vendors, see [Grepr supported vendor and storage integrations](/integrations/support-matrix).
-> * To show you the most direct way to create a pipeline in the Grepr UI, this tutorial walks you through creating an end-to-end pipeline directly in the Grepr pipeline editor. However, to give you more control over configurations, the Grepr UI also includes separate interfaces to configure pipeline components such as integrations.
-> * This tutorial shows you how to send logs to Grepr using Datadog agents running in local Docker containers. However, if you have existing infrastructure forwarding logs to Datadog, you can use that infrastructure for this example. The Grepr Datadog integration also supports log collectors other than Datadog agents. To learn more about supported collectors, including configuration details, see [Configure Datadog connections with a Grepr integration](/integrations/datadog).
-
-## Requirements
-
-To complete this tutorial, you must have:
-
-* A Grepr account and a login to your organization's Grepr UI. If you don't have a Grepr account, sign up at <https://app.grepr.ai/signup>.
-* An organization identifier. A 3–31 character identifier containing only lowercase letters, numbers, and hyphens. If you don't have one, create an organization ID when you sign up for a Grepr account.
-* An account with an observability vendor supported by Grepr. This tutorial uses Datadog. If you don't have a Datadog account, you can sign up for a free trial at [www.datadoghq.com](https://www.datadoghq.com). For the complete list of supported observability vendors, see [Grepr supported vendor and storage integrations](/integrations/support-matrix).
-* A Datadog API key for your account. You can retrieve this from your Datadog Organization Settings or copy it from the Agent Setup page instructions.
-* The Datadog site parameter that the Datadog agents should use. This parameter is determined by the Datadog site you selected. For example, if you select `US1`, the site parameter's value is `datadoghq.com`.
-* A Docker installation in your local environment. Docker is used to run the Datadog agents that send log events to Grepr.
-
-## Step 1: Verify that agents can send events to Datadog
-
-Before working through this tutorial, you should verify that Datadog agents running in your local environment can send log events directly to Datadog. In a terminal window, run the following command, replacing `DD_API_KEY_VALUE` with your Datadog API key and `DD_SITE_VALUE` with your Datadog site parameter. Optionally replace `DD_HOSTNAME` with a preferred hostname for testing. This value can be used in the Datadog UI to filter incoming log events:
-
-```bash
-docker run --rm --name dd-agent \
--e DD_API_KEY=DD_API_KEY_VALUE \
--e DD_SITE="datadoghq.com" \
--e DD_LOGS_ENABLED=true \
--e DD_LOGS_CONFIG_CONTAINER_COLLECT_ALL=true \
--e DD_HOSTNAME=my-test-host \
--v /var/run/docker.sock:/var/run/docker.sock:ro \
--v /proc/:/host/proc/:ro \
--v /sys/fs/cgroup/:/host/sys/fs/cgroup:ro \
-gcr.io/datadoghq/agent:latest
-```
-
-While this command runs, go to the Datadog UI, click **Logs**, and then click **Live Tail**. If everything's working correctly, you see log events arriving from the Datadog agent.
-
-To learn more about the Datadog Docker Agent, including details for the configuration options, see the [Datadog documentation](https://docs.datadoghq.com/containers/docker/).
-
-When you've finished testing, shut down the agent by running the following command in a separate terminal:
-
-```bash
-docker stop dd-agent
-```
-
-## Step 2: Create a Grepr pipeline to process log events
-
-A Grepr pipeline defines the steps to process log data. Pipelines you create in the Grepr UI implement a flow with the following steps to reduce the volume of log data sent to your observability platform:
-
-* Read logs from one or more sources. Sources use Grepr integrations that connect Grepr to external systems, such as observability vendors or cloud storage providers. This tutorial guides you through creating a source that uses a Grepr Datadog integration.
-
-* Filter log events at several stages in the pipeline.
-
-* Extract structured data from unstructured log messages or attributes using the Grepr Grok parser. See the [Grok parser](/transforms/grok) documentation.
-
-* Persist the raw logs into your Grepr data lake. To add a data lake in the pipeline editor, you must have a Grepr storage integration and a Grepr dataset configured.
-
-  * The storage integration is used to ensure retention of all data by storing raw logs in low-cost cloud storage. This tutorial uses a storage integration that uses a Grepr-hosted Amazon S3 bucket.
-  * The dataset defines a namespace in your storage specifying where the raw logs are stored.
-
-* Reduce the amount of log data to forward to your observability platform through the log reducer. To learn more about the log reducer, see [Reduce shipped data volumes with the Grepr log reducer](/transforms/reducer).
-
-* Send the result of processing the logs to one or more sinks. Like sources, sinks use a configured Grepr integration.
-
-To create pipelines with more complex functionality, you can use the Grepr REST API. See the [Job creation API guide](/apis/job-creation-guide).
-
-To create a new pipeline:
-
-1. In the Grepr UI, click **Home** in the navigation menu, then click **Create Pipeline**.
-
-2. In the **Create Pipeline** dialog, enter a name for your new pipeline.
-
-3. Click **Create**.
-
-After clicking **Create**, the pipeline editor view appears. The left pane displays the flow for a log reduction pipeline. In the next step, you begin configuring the pipeline by adding a source.
-
-### Add a source for Datadog logs
-
-To add a source in the pipeline editor, you first configure a Grepr integration. To create an integration and add a source:
-
-1. Click **Continue** in the pipeline editor view.
-
-2. Click **Add integration**.
-
-3. In the **Add Observability Vendor** dialog:
-
-   * In the **Type** menu, select **Datadog**.
-   * In the **Name** field, enter a name for the integration.
-   * In the **Site** menu, select the parameter matching your Datadog site.
-   * In the **API Key** field, enter your Datadog API key.
-   * Leave the **Application Key** field empty.
-
-4. Click **Create**.
-
-   After clicking **Create**, Grepr validates the API key with Datadog, creates the integration, and returns a success message. If any issues are found, an error message is returned instead.
-
-5. In the **Add source** dialog, select the Datadog integration you created in the previous step. A name for this source is automatically added for you.
-
-6. Click **Submit**.
-
-### Add a data lake
-
-To add a Grepr data lake to retain raw log data, you first configure a Grepr storage integration. To create a storage integration and add a data lake to your pipeline:
-
-1. Click **Data Lake** in the left pane, then click **Add**.
-
-2. In the **Add Data Lake** dialog:
-
-   * In the **Type** menu, select **Grepr-hosted**.
-   * In the **Name** field, enter a name for the integration.
-
-3. Click **Next**.
-
-4. In the **Dataset Name** field, enter a name for the dataset to contain raw data. This can be any name you choose, but it should be descriptive.
-
-5. In the **Integration** menu, select the storage integration you created in the previous step.
-
-6. Click **Add**.
-
-To send the processed logs to Datadog, a sink is automatically added to your pipeline. Click **Sinks** in the left pane to view the sink. Under **Additional Tags / Attributes**, you can see automatically populated tags. These tags are appended to messages before they're sent to Datadog. Grepr recommends retaining these tags because they allow you to distinguish Grepr-processed logs from other logs.
-
-## Step 3: Create and start the pipeline
-
-Click **Create Pipeline** in the top bar, then click **Confirm** in the **Create pipeline** dialog. Your pipeline will shortly go from **Starting** to **Running**. When the pipeline reaches the **Running** state, it's ready to start processing logs. In the next step, you simulate sending log messages through your pipeline.
-
-## Step 4: Simulate multiple agents sending logs through Grepr
-
-1. Before sending log messages to your pipeline, make sure no Docker containers are running the Datadog agent. In a terminal, run the following command:
-
-   ```bash
-   docker stop dd-agent
-   ```
-
-2. To configure the Datadog agents to send logs to Grepr, you need the Grepr ingestion URL. To find the URL, click **Sources** in the left pane and copy the **Ingest URL** value.
-
-3. To start five agents to send logs through Grepr, run the following command, replacing `INGESTION_URL` with the Grepr ingestion URL you copied above, and `DD_API_KEY_VALUE` with your Datadog API key:
-
-   ```bash
-   for i in $(seq 1 5); do docker run -d --rm --name dd-agent-$i \
-   -e DD_API_KEY=DD_API_KEY_VALUE \
-   -e DD_SITE="datadoghq.com" \
-   -e DD_LOGS_ENABLED=true \
-   -e DD_LOGS_CONFIG_CONTAINER_COLLECT_ALL=true \
-   -e DD_HOSTNAME=my-test-host-$i \
-   -v /var/run/docker.sock:/var/run/docker.sock:ro \
-   -v /proc/:/host/proc/:ro \
-   -v /sys/fs/cgroup/:/host/sys/fs/cgroup:ro \
-   -e DD_LOGS_CONFIG_LOGS_DD_URL=INGESTION_URL \
-   -e DD_LOGS_CONFIG_USE_HTTP="true" \
-   gcr.io/datadoghq/agent:latest; done
-   ```
-
-   This command starts five agents, each with a different hostname. There are two new environment variables added to the command: `DD_LOGS_CONFIG_LOGS_DD_URL` and `DD_LOGS_CONFIG_USE_HTTP`. The first variable provides the agents with the Grepr URL to send logs to, and the second variable tells the agents to use HTTPS instead of TCP when sending logs to Grepr.
-
-   > Before sending logs for ingestion, ensure there's at least one running pipeline that includes a Datadog source that matches the Datadog integration you created in Step 2. If a pipeline doesn't exist, the ingestion requests are not accepted.
-
-## View the results
-
-After the agents are running, to monitor log ingestion activity, go to the Grepr Pipelines UI and select **Overview**.
-
-To see the logs arriving to Datadog, go to the Datadog **Log Explorer**. To filter for only messages arriving from your test agents, enter `host:my-test-host*` in the **Filter your logs** text box.
-
-When you scroll through the logs in the Datadog **Log Explorer**, you can see that repeated log events are aggregated. This aggregation, which reduces the data volumes sent to Datadog, is the result of the Grepr log reducer. To learn more about the log reducer, see [Reduce shipped data volumes with the Grepr log reducer](/transforms/reducer).
-
-## Cleaning up
-
-When you've finished the tutorial, you can stop the Datadog agents by running the following command in a terminal:
-
-```bash
-for i in $(seq 1 5); do docker stop dd-agent-$i; done
-```
-
-To stop the pipeline, go to the Grepr UI home page, click the **More options** icon (⋮) in the top-right corner of the pipeline card, select **Stop**, and then confirm that you would like to stop the pipeline.
-
-## Next steps
-
-To see an example of troubleshooting incidents with Grepr and Datadog, see the [troubleshooting tutorial](/tutorials/troubleshooting-example).
-
-## Frequently Asked Questions
-
-### What is a Grepr pipeline?
-
-A Grepr pipeline is a configurable data processing workflow that reads logs from sources, applies filters and transformations, optionally stores raw logs in a data lake, reduces log volume using intelligent aggregation, and sends processed logs to sinks. Pipelines allow you to dynamically control log volumes without losing important data.
-
-### How do I create my first Grepr pipeline?
-
-To create your first pipeline, sign in to the Grepr UI, click 'Create Pipeline' on the Home page, enter a name, and click Create. The pipeline editor will open where you can add sources, configure integrations, set up storage, and create sinks. This tutorial walks through the complete process with a Datadog example.
-
-### What observability platforms does Grepr support?
-
-Grepr supports multiple observability vendors, including Datadog, Splunk, New Relic, and others. For a complete list of supported platforms and regions, see the Grepr supported vendor and storage integrations documentation.
-
-### Do I need a Datadog account to follow this tutorial?
-
-Yes, this tutorial uses Datadog as an example. However, you can follow the same steps with any Grepr-supported observability platform. If you don't have a Datadog account, sign up for a free trial at www\.datadoghq.com or use your preferred observability platform.
-
-### What is the log reducer and how does it work?
-
-The log reducer is a Grepr component that intelligently aggregates repeated log events into summary messages, reducing the volume of logs sent to your observability platform. It identifies patterns in logs and uses placeholders for varying fields, allowing you to maintain visibility while reducing storage and processing costs.
-
-### How do I configure a Datadog integration in Grepr?
-
-To configure a Datadog integration, click 'Add integration' in the pipeline editor, select Datadog as the Type, enter a name for the integration, select your Datadog site from the menu, and enter your Datadog API key. Click Create and Grepr will validate the API key with Datadog.
-
-### What is the Grepr data lake and why do I need it?
-
-The Grepr data lake is a storage system that retains all raw log data in low-cost cloud storage using a Grepr-hosted Amazon S3 bucket. It ensures you don't lose any data while using the log reducer and allows you to backfill logs or perform historical analysis later.
-
-### How do I monitor logs flowing through my pipeline?
-
-You can monitor log ingestion in the Grepr Pipelines UI by selecting 'Overview' to see real-time event metrics. Additionally, go to your observability platform (Datadog, Splunk, etc.) to see the processed logs after reduction. In Datadog, filter using labels like 'host:my-test-host\*' to see logs from your test agents.
-
-### What happens to logs after the log reducer aggregates them?
-
-After the log reducer aggregates logs into summary messages, they are sent to your observability platform sinks. The summary messages include metadata like repeat count, first/last timestamps, and a pattern ID, allowing you to trace back to raw logs stored in the data lake if needed.
-
-### Can I test my pipeline changes before applying them to production?
-
-Yes, Grepr provides a live edit feature that allows you to safely test changes to your pipeline without impacting production. Live edit creates a temporary copy of your pipeline and excludes sinks, preventing duplicate data from being sent to your observability platform.

package/build/dist/docs-index/d95717b3-1911-4ead-8188-d5c6ab3a1bba.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/d95717b3-1911-4ead-8188-d5c6ab3a1bba.txt

@@ -1,30 +0,0 @@
-# Apply masks to samples
-
-**POST** `/v1/masking/mask`
-
-**Operation ID**: `mask`
-**Summary**: Apply masks to samples
-Applies a masking operator's masks to sample log events and returns the masked result for each, so the editor can preview a configuration without deploying it. The operator's predicate gates which logs are masked in production, not how, so it is ignored here and the masks are applied to every sample.
-
-## Tags
-- Masking
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `MaskingRequest`
-
-## Responses
-
-### 200
-
-Sample masked successfully.
-
-- **Content-Type**: `application/json` / `MaskingResponse`
-### 400
-
-The masking configuration is invalid or could not be compiled.
-
-### 401
-
-Unauthorized

package/build/dist/docs-index/d979ea8f-7ec5-4d27-b3e9-df4b67aec2da.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/d979ea8f-7ec5-4d27-b3e9-df4b67aec2da.txt

@@ -1,15 +0,0 @@
-# getUserPermissions
-
-**GET** `/v1/me/permissions`
-
-**Operation ID**: `getUserPermissions`
-**Summary**: No summary provided.
-## Tags
-- Users
-## Responses
-
-### default
-
-default response
-
-- **Content-Type**: `application/json` / `UserPermissionsResponse`

package/build/dist/docs-index/d9d16fd5-28c7-4b37-b49d-e6b1c597a3d0.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/d9d16fd5-28c7-4b37-b49d-e6b1c597a3d0.txt

@@ -1,15 +0,0 @@
-# IssueScopeView
-
-Which issues a principal may act on for one action: every issue in the organization, or those naming one of these teams.
-
-**Type**: `object`
-
-## Properties
-
-- name: orgWide (optional)
-  type: boolean
-  description: Whether the principal may act on every issue in the organization.
-
-- name: teamIds (optional)
-  type: array of string
-  description: The teams whose issues the principal may act on, sorted; empty when `orgWide`.

package/build/dist/docs-index/da5029e7-ed89-4427-a9d2-4f3c811d3af1.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/da5029e7-ed89-4427-a9d2-4f3c811d3af1.txt

@@ -1,11 +0,0 @@
-# TagCountItem
-
-**Type**: `object`
-
-## Properties
-
-- name: count (optional)
-  type: integer
-
-- name: name (optional)
-  type: string

package/build/dist/docs-index/dab55349-2af8-40d3-8dea-25fe363a89d4.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/dab55349-2af8-40d3-8dea-25fe363a89d4.txt

@@ -1,15 +0,0 @@
-# SortFieldConfig
-
-User-chosen sort fields, in precedence order.
-
-**Type**: `object`
-
-## Properties
-
-- name: column (required)
-  type: string
-  description: Built-in column or an attribute key to sort by.
-
-- name: direction (optional)
-  type: enum: `ASC`, `DESC`
-  description: Sort direction for this field.

package/build/dist/docs-index/dac958ad-7daf-4e78-8524-0768caf550f0.json

@@ -1 +0,0 @@
-{"docType":"api"}