@grepr/cli 1.9.2-fc34d73 → 1.9.3-15ebe91

package/build/dist/docs-index/3a265e07-ba74-4189-bf93-6f2745cce695.txt

@@ -1,24 +0,0 @@
-# Delete a S3 Data Warehouse integration
-
-**DELETE** `/v1/integrations/s3-data-warehouse/{id}`
-
-**Operation ID**: `delete_4`
-**Summary**: Delete a S3 Data Warehouse integration
-Deletes an external S3 Data Warehouse integration if it exists. No-op otherwise.
-
-## Tags
-- External S3 Data Warehouse Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Responses
-
-### 200
-
-S3 Data Warehouse integration deleted successfully
-
-### 401
-
-Unauthorized

package/build/dist/docs-index/3d25bf1e-e5c2-436a-a254-d9565356ef99.txt

@@ -1,24 +0,0 @@
-# Delete an S3 Vector Index integration
-
-**DELETE** `/v1/integrations/s3-vector-index/{id}`
-
-**Operation ID**: `delete_13`
-**Summary**: Delete an S3 Vector Index integration
-Deletes an S3 Vector Index integration and removes the index from the S3 vector bucket. No-op if integration doesn't exist.
-
-## Tags
-- S3 Vector Index Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Responses
-
-### 200
-
-S3 Vector Index integration deleted successfully
-
-### 401
-
-Unauthorized

package/build/dist/docs-index/3eb8b714-c767-41d3-8d2f-85560b64522d.txt

@@ -1,31 +0,0 @@
-# List all users
-
-**GET** `/v1/users`
-
-**Operation ID**: `list_17`
-**Summary**: List all users
-Get all users in the system.
-
-## Tags
-- Users
-## Parameters
-
-- **page** (optional) - query
-  - Type: integer
-- **pageSize** (optional) - query
-  - Type: integer
-
-## Responses
-
-### 200
-
-Users retrieved successfully
-
-- **Content-Type**: `application/json` / `UsersListInfos`
-### 401
-
-Unauthorized
-
-### 403
-
-Unauthorized

package/build/dist/docs-index/4075c75b-2759-44a8-a4f0-8f6e9df2773c.txt

@@ -1,32 +0,0 @@
-# Create a Slack MCP integration
-
-**POST** `/v1/integrations/slack-mcp`
-
-**Operation ID**: `create_9`
-**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/435748b0-96c8-4acb-8969-604217f177a7.txt

@@ -1,32 +0,0 @@
-# Create an OTLP integration
-
-**POST** `/v1/integrations/otlp`
-
-**Operation ID**: `create_12`
-**Summary**: Create an OTLP integration
-Creates an integration to connect to OTLP.
-
-## Tags
-- OpenTelemetry Integration
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `WriteOtlp`
-
-## Responses
-
-### 200
-
-Integration created successfully
-
-- **Content-Type**: `application/json` / `ReadOtlp`
-### 401
-
-Unauthorized
-
-### 409
-
-Integration already exists.
-
-- **Content-Type**: `application/json` / `ReadOtlp`

package/build/dist/docs-index/45f45d25-9b39-4d92-8907-942a64497731.txt

@@ -1,40 +0,0 @@
-# TraceReducer
-
-Reduces trace volume by applying a uniform trace head sampling rate and configurable span head sampling rules with optional tail sampling, then emits the retained spans.
-
-**Type**: `object`
-
-## Properties
-
-- name: actions (optional)
-  type: array of `TraceAction`
-  description: Actions to execute on traces. Actions process spans after sampling decisions have been made and can trigger operations like logs backfill.
-
-- name: criticalPathAnalysis (optional)
-  type: `CriticalPathAnalysisConfig`
-
-- name: datasetId (optional)
-  type: string
-  description: Dataset ID used for naming the Iceberg table (traces_raw_{datasetId}). If not provided, traces will not be persisted to Iceberg.
-
-- name: name (required)
-  type: string
-
-- name: spanHeadSamplingRules (optional)
-  type: array of `SpanHeadSamplingRule`
-  description: Span head sampling rules. Matched spans are retained as SPAN_HEAD_SAMPLED. If tail sampling is configured, matched spans participate in trace assembly before output; otherwise, matched spans are emitted directly. Order is significant; first match wins for metric attribution. Trace head sampling wins when both match the same span.
-
-- name: tailSampling (optional)
-  type: `TailSamplingConfig`
-
-- name: traceHeadSamplingRate (optional)
-  type: number
-  description: Uniform trace head sampling rate in [0.0, 1.0]. When set, all spans sharing a traceId are retained together as HEAD_SAMPLED at this probability. Mutually exclusive with traceHeadSamplingRules (scalar wins when both present).
-
-- name: traceHeadSamplingRules (optional)
-  type: array of `TraceHeadSamplingRule`
-  description: Deprecated: use traceHeadSamplingRate instead. Kept for backwards compatibility with stored configurations. When traceHeadSamplingRate is absent, the effective rate is max(rate) over this list (filters are ignored).
-
-- name: type (required)
-  type: enum: `trace-reducer`
-  description: Reduces trace volume by sampling CompleteSpan instances. Combines a uniform trace head sampling rate (whole-trace retention) and per-span head sampling rules with optional quantile-based tail sampling.

package/build/dist/docs-index/483615e4-6fe8-47d7-b889-d00da59121c4.txt

@@ -1,20 +0,0 @@
-# List all Datadog MCP integrations
-
-**GET** `/v1/integrations/datadog-mcp`
-
-**Operation ID**: `list_6`
-**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/4c2bd154-1462-4262-b369-66ac10478407.txt

@@ -1,29 +0,0 @@
-# AgentConfigCreate
-
-**Type**: `object`
-
-## Properties
-
-- name: enabledMcpIntegrations (required)
-  type: array of `AgentMcpIntegrations`
-
-- name: enabledSkills (required)
-  type: array of string
-
-- name: enabledTools (required)
-  type: array of string
-
-- name: maxTokens (optional)
-  type: integer
-
-- name: maxTurns (optional)
-  type: integer
-
-- name: modelConfiguration (required)
-  type: `ModelConfiguration`
-
-- name: name (required)
-  type: string
-
-- name: systemPrompt (required)
-  type: string

package/build/dist/docs-index/4cf6be7e-8b71-41d2-a0fa-dba025a7a5bf.txt

@@ -1,28 +0,0 @@
-# Delete an agent
-
-**DELETE** `/v1/agents/{id}`
-
-**Operation ID**: `delete`
-**Summary**: Delete an agent
-Soft-deletes an agent. Returns 409 while the agent is still subscribed to any pipeline; unsubscribe it first.
-
-## Tags
-- Agents
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Responses
-
-### 204
-
-Agent deleted successfully
-
-### 401
-
-Unauthorized
-
-### 409
-
-Agent is still subscribed to one or more pipelines

package/build/dist/docs-index/4efc839d-ade4-46bc-8c30-faae9b4a62cd.txt

@@ -1,29 +0,0 @@
-# Get a NewRelic integration
-
-**GET** `/v1/integrations/newrelic/{id}`
-
-**Operation ID**: `get_10`
-**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/51385065-96f7-4481-bacd-e8e391d0e7e8.txt

@@ -1,20 +0,0 @@
-# List all OTLP integrations
-
-**GET** `/v1/integrations/otlp`
-
-**Operation ID**: `list_12`
-**Summary**: List all OTLP integrations
-Get all OTLP integrations.
-
-## Tags
-- OpenTelemetry Integration
-## Responses
-
-### 200
-
-Integrations retrieved successfully
-
-- **Content-Type**: `application/json` / `ItemsCollectionReadOtlp`
-### 401
-
-Unauthorized

package/build/dist/docs-index/55c63f29-ca5c-4b5e-971a-358f3163289b.txt

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

package/build/dist/docs-index/57932f88-32d0-4a29-a389-a17f869440d0.txt

@@ -1,20 +0,0 @@
-# List agents
-
-**GET** `/v1/agents`
-
-**Operation ID**: `list`
-**Summary**: List agents
-Returns every agent configured for your organization, newest first.
-
-## Tags
-- Agents
-## Responses
-
-### 200
-
-Agents retrieved successfully
-
-- **Content-Type**: `application/json` / array of `AgentSummary`
-### 401
-
-Unauthorized

package/build/dist/docs-index/5dab1302-8d31-4f67-b2fd-0db6cfd684b9.txt

@@ -1,24 +0,0 @@
-# Delete a webhook integration
-
-**DELETE** `/v1/integrations/webhooks/{id}`
-
-**Operation ID**: `delete_16`
-**Summary**: Delete a webhook integration
-Deletes a webhook integration. No-op if already deleted.
-
-## Tags
-- Webhook Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Responses
-
-### 204
-
-Integration deleted successfully
-
-### 401
-
-Unauthorized

package/build/dist/docs-index/61ee6968-c2c3-4fd7-9b4b-825463eb1768.txt

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

package/build/dist/docs-index/6cc87586-ff6a-4a1c-a702-827ea199721b.txt

@@ -1,32 +0,0 @@
-# AgentConfigUpdate
-
-**Type**: `object`
-
-## Properties
-
-- name: enabledMcpIntegrations (required)
-  type: array of `AgentMcpIntegrations`
-
-- name: enabledSkills (required)
-  type: array of string
-
-- name: enabledTools (required)
-  type: array of string
-
-- name: maxTokens (optional)
-  type: integer
-
-- name: maxTurns (optional)
-  type: integer
-
-- name: modelConfiguration (required)
-  type: `ModelConfiguration`
-
-- name: name (required)
-  type: string
-
-- name: systemPrompt (required)
-  type: string
-
-- name: version (optional)
-  type: integer

package/build/dist/docs-index/6d0552b5-e9cf-4090-8e72-bab19ae87367.txt

@@ -1,32 +0,0 @@
-# Create a GitHub MCP integration
-
-**POST** `/v1/integrations/github-mcp`
-
-**Operation ID**: `create_7`
-**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/6e03c14f-cb66-490f-9a02-bbf02c35e65a.txt

@@ -1,151 +0,0 @@
-Grepr's security program is SOC 2 Type II certified and HIPAA attested, with enterprise infrastructure, compliance, and data protection for observability.
-
-# Security in the Grepr platform
-
-At Grepr, security is foundational to everything Grepr builds. The robust security program ensures your data remains protected, meeting stringent compliance requirements while enabling your business to operate with confidence.
-
-## Trust and compliance
-
-### SOC 2 Type II certification
-
-Grepr has successfully completed a SOC 2 Type II audit by an independent third-party auditor, verifying that security controls are not only well-designed but operating effectively over time. This rigorous assessment validates commitment to:
-
-* **Security**: Protecting customer data and systems from unauthorized access.
-* **Availability**: Ensuring systems are available as committed.
-* **Processing integrity**: Processing data completely, accurately, and in a timely manner.
-* **Confidentiality**: Protecting information designated as confidential.
-* **Privacy**: Handling personal information in accordance with privacy commitments.
-
-To request the complete SOC 2 Type II report, please contact the [security team](mailto:security@grepr.io).
-
-### HIPAA compliance
-
-Grepr has completed a HIPAA attestation performed by A-lign, the same independent auditor that conducts the SOC 2 Type II audit. The attestation verifies that the controls safeguarding *protected health information* are designed and operating effectively.
-
-If your organization requires a Business Associate Agreement (BAA), Grepr signs one. To request a BAA or the complete HIPAA attestation report, please contact the [security team](mailto:security@grepr.io).
-
-To learn more about subprocessors and compliance certifications, see the [Trust Center](https://trust.grepr.ai/).
-
-## Security architecture
-
-### Authenticate to the Grepr platform
-
-* **Secure identity management**: Authentication to the Grepr UI uses OAuth 2.0 with [Auth0](https://auth0.com/). Grepr supports SAML as well as OpenID Connect (OIDC) to ease and secure identity management for customers.
-* **API security**: All Grepr APIs implement OAuth 2.0 for robust authentication and authorization.
-* **Zero credential storage**: Grepr does not store your passwords or credentials in data stores. Grepr partners with [Auth0](https://auth0.com/) for secure identity and access management.
-* **Role-based access controls**: Granular permissions ensure you can only access the resources you need.
-
-### Infrastructure security
-
-* **Amazon Web Services (AWS) enterprise infrastructure**: The production environment runs on AWS, utilizing industry-leading security features and best practices.
-* **Network isolation**: All server infrastructure resides within dedicated AWS Virtual Private Clouds (VPCs) with no direct internet accessibility.
-* **Data encryption**: Data is encrypted both in transit (Transport Layer Security (TLS) 1.2+) and at rest using strong encryption standards.
-* **Secure data architecture**: Grepr implements efficient data storage using Apache Parquet and Apache Iceberg table formats, with raw data secured in Amazon S3.
-* **API key security**: API keys are securely stored in AWS Secrets Manager with strict access controls.
-
-### Vulnerability management and remediation
-
-* **Continuous vulnerability scanning**: Infrastructure and applications undergo regular automated and manual security scans to identify potential vulnerabilities.
-* **Software composition analysis**: Grepr continuously monitors software dependencies and libraries for known vulnerabilities through automated tools integrated into the CI/CD pipeline.
-* **Rapid remediation**: Critical vulnerabilities are addressed within 24 hours, with clear Service Level Agreements (SLAs) for all severity levels.
-* **Patch management**: Grepr maintains a structured process for timely application of security patches across infrastructure and application stack.
-* **Third-party security assessments**: Regular independent security assessments complement the internal vulnerability management program.
-
-### Proactive security operations
-
-* **Continuous monitoring**: Advanced monitoring, alerting, and intrusion detection systems provide real-time visibility into security posture.
-* **Threat intelligence**: Grepr leverages industry threat intelligence to stay ahead of emerging security threats.
-* **Penetration testing**: Independent third-party security firms conduct regular penetration tests of infrastructure and applications. Reports are available upon request.
-
-## Enterprise security program
-
-### Governance and risk management
-
-* **Security policies**: Grepr maintains formal, regularly-reviewed policies covering information security, risk management, and operational security.
-* **Risk assessment**: Systematic evaluation processes identify, assess, and mitigate security risks.
-* **Vendor security assessment**: Grepr rigorously evaluates third-party vendors to ensure they meet security standards.
-
-### Employee security
-
-* **Security training**: All employees complete mandatory security awareness training upon joining and regularly thereafter.
-* **Secure development**: Engineers follow secure coding practices, with security reviews integrated throughout the development lifecycle.
-* **Access controls**: Grepr enforces least-privilege access controls and multi-factor authentication for all staff.
-
-### Business continuity
-
-* **Disaster recovery**: Disaster recovery plans ensure business continuity in adverse situations.
-* **Data backups**: Regular data backups with verified recovery procedures protect your information.
-* **High availability design**: The architecture minimizes single points of failure for critical systems.
-
-### Incident response
-
-* **Incident management framework**: A formal incident response plan guides handling of security events.
-* **Response team**: The dedicated security team is prepared to respond rapidly to security incidents.
-* **Breach notification**: Clear procedures ensure timely and appropriate communications in the event of a security incident.
-
-## Deployment options
-
-* **Software as a Service (SaaS) deployment**: The standard cloud offering provides enterprise security with minimal overhead.
-* **Private cloud**: For organizations with strict compliance requirements, Grepr offers private cloud deployment options.
-
-## Security assurance
-
-Grepr understands that enterprise buyers require ongoing assurance of security practices:
-
-* **Regular attestations**: The SOC 2 Type II certification and the HIPAA attestation are renewed annually.
-* **Transparency**: Grepr is committed to clear communication about security practices.
-* **Continuous improvement**: The security program evolves with emerging threats and best practices.
-
-## Contact the security team
-
-For detailed security information, compliance documentation, or to report security concerns, please contact the security team at <security@grepr.io>.
-
-## Frequently Asked Questions
-
-### Is Grepr SOC 2 certified?
-
-Yes, Grepr has completed a SOC 2 Type II audit verifying that security controls are well-designed and operating effectively. The certification covers security, availability, processing integrity, confidentiality, and privacy.
-
-### Is Grepr HIPAA compliant?
-
-Yes, Grepr has completed a HIPAA attestation performed by A-lign, the same independent auditor that conducts the SOC 2 Type II audit. The attestation verifies that the controls safeguarding protected health information are designed and operating effectively.
-
-### Does Grepr sign a Business Associate Agreement?
-
-Yes, Grepr signs a Business Associate Agreement (BAA) with any customer that requires one. To request a BAA, contact the security team at security\@grepr.io.
-
-### How does Grepr authenticate users?
-
-Grepr uses OAuth 2.0 with Auth0 for UI authentication and supports SAML and OpenID Connect (OIDC) for enterprise identity management. Grepr does not store passwords or credentials directly.
-
-### How are Grepr APIs secured?
-
-All Grepr APIs implement OAuth 2.0 for robust authentication and authorization. Access tokens are obtained from Auth0 and must be included as Bearer tokens in API requests.
-
-### How is data encrypted in Grepr?
-
-Data is encrypted in transit using TLS 1.2 or higher and at rest using strong encryption standards. API keys are securely stored in AWS Secrets Manager with strict access controls.
-
-### What infrastructure does Grepr use?
-
-Grepr runs on Amazon Web Services (AWS) enterprise infrastructure with dedicated Virtual Private Clouds (VPCs). The infrastructure includes network isolation, advanced monitoring, and automated security scanning.
-
-### How does Grepr manage vulnerabilities?
-
-Grepr conducts continuous automated and manual security scans, monitors software dependencies for known vulnerabilities, and maintains strict SLAs for remediation (24 hours for critical vulnerabilities).
-
-### Does Grepr perform penetration testing?
-
-Yes, independent third-party security firms conduct regular penetration tests of Grepr infrastructure and applications. Penetration testing reports are available upon request.
-
-### What are Grepr's access control practices?
-
-Grepr enforces least-privilege access controls for all staff, requires multi-factor authentication, and implements role-based access controls (RBAC) for granular permissions.
-
-### How does Grepr handle security incidents?
-
-Grepr maintains a formal incident response plan with a dedicated security team prepared to respond rapidly. Clear procedures ensure timely notification in the event of a security incident.
-
-### Can I get the complete Grepr security documentation?
-
-Yes, contact the security team at security\@grepr.io to request the complete SOC 2 Type II report, the HIPAA attestation report, a Business Associate Agreement (BAA), subprocessor information, compliance certifications, and other security documentation.

package/build/dist/docs-index/703e7935-c2ab-461d-90fd-d6205e94e42f.txt

@@ -1,46 +0,0 @@
-# CompleteSpan
-
-A complete span with its resource and instrumentation scope context.
-
-**Type**: `object`
-
-## Properties
-
-- name: critPathNs (optional)
-  type: integer
-
-- name: critPathPct (optional)
-  type: number
-
-- name: duration (optional)
-  type: integer
-
-- name: eventTimestamp (optional)
-  type: integer
-
-- name: hasError (optional)
-  type: boolean
-
-- name: percentileBucket (optional)
-  type: string
-
-- name: receivedTimestamp (optional)
-  type: integer
-
-- name: resource (optional)
-  type: `Resource`
-
-- name: samplingType (optional)
-  type: integer
-
-- name: scope (optional)
-  type: `InstrumentationScope`
-
-- name: serviceName (optional)
-  type: string
-
-- name: span (optional)
-  type: `Span`
-
-- name: traceSignature (optional)
-  type: string