@grepr/cli 1.11.5-967ecba → 1.11.5-c840124

package/build/dist/docs-index/3240f10b-3e99-4da1-b706-9485440a6beb.txt

@@ -0,0 +1,39 @@
+# Preview authorization scopes for unsaved changes to an integration
+
+**POST** `/v1/integrations/datadog/{id}/app-key/scopes/preview`
+
+**Operation ID**: `previewDatadogAppKeyScopes`
+**Summary**: Preview authorization scopes for unsaved changes to an integration
+Probes Datadog with the integration's stored keys, overridden by whatever the body supplies, and reports each authorization scope. Nothing is written. An omitted field means "use what is stored", so an empty body reports what the stored key can do right now. A scope whose probe does not complete is reported UNKNOWN rather than as a permission the user has to grant.
+
+## Tags
+- Datadog Integration
+## Parameters
+
+- **id** (required) - path
+  - Type: string
+
+## Request Body
+
+**Content-Type**: `application/json`
+
+**Schema**: `PreviewAppKeyScopesRequest`
+
+## Responses
+
+### 200
+
+Scopes checked successfully
+
+- **Content-Type**: `application/json` / array of `AppKeyScopeCheck`
+### 400
+
+The supplied site is not allowed for this organization.
+
+### 401
+
+Unauthorized
+
+### 404
+
+Integration not found.

package/build/dist/docs-index/4d9f94bf-f7f8-42c6-84f7-fb237e5e89ec.txt

@@ -0,0 +1,19 @@
+# CheckAppKeyScopesRequest
+
+Keys and site to check Datadog authorization scopes against
+
+**Type**: `object`
+
+## Properties
+
+- name: apiKey (required)
+  type: string
+  description: API key to authenticate the probes with
+
+- name: appKey (required)
+  type: string
+  description: Application key to check
+
+- name: site (required)
+  type: string
+  description: The Datadog site to probe

package/build/dist/docs-index/9f8e5c18-e8bf-4771-b9f4-87f9ba8995ee.txt

@@ -0,0 +1,19 @@
+# AppKeyScopeCheck
+
+Whether a Datadog application key holds one authorization scope
+
+**Type**: `object`
+
+## Properties
+
+- name: required (optional)
+  type: boolean
+  description: Whether Grepr rejects an application key without this scope
+
+- name: scope (optional)
+  type: string
+  description: The Datadog authorization scope identifier
+
+- name: status (optional)
+  type: enum: `GRANTED`, `DENIED`, `UNKNOWN`
+  description: Whether the application key was found to hold a scope, or could not be checked

package/build/dist/docs-index/c1856e28-f8f0-41b8-9705-72c0201228a5.txt

@@ -0,0 +1,30 @@
+# Preview authorization scopes for keys not yet saved to any integration
+
+**POST** `/v1/integrations/datadog/app-key/scopes/preview`
+
+**Operation ID**: `previewNewDatadogAppKeyScopes`
+**Summary**: Preview authorization scopes for keys not yet saved to any integration
+Probes Datadog with the supplied site and keys and reports each authorization scope. For the create form, where there is no integration to take keys from, so every field is required. Nothing is written and nothing is stored.
+
+## Tags
+- Datadog Integration
+## Request Body
+
+**Content-Type**: `application/json`
+
+**Schema**: `CheckAppKeyScopesRequest`
+
+## Responses
+
+### 200
+
+Scopes checked successfully
+
+- **Content-Type**: `application/json` / array of `AppKeyScopeCheck`
+### 400
+
+The supplied site is not allowed for this organization.
+
+### 401
+
+Unauthorized

package/build/dist/docs-index/c9bfeb80-2217-45c6-9380-8310be3d72cf.txt

@@ -0,0 +1,19 @@
+# PreviewAppKeyScopesRequest
+
+Unsaved changes to check Datadog authorization scopes against
+
+**Type**: `object`
+
+## Properties
+
+- name: apiKey (optional)
+  type: string
+  description: API key to probe with instead of the stored one
+
+- name: appKey (optional)
+  type: string
+  description: Application key to check instead of the stored one
+
+- name: site (optional)
+  type: string
+  description: Site to probe instead of the stored one