Skip to content

chore(spec): add missing descriptions [cloud-security-posture-management] #3597

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
api-clients-generation-pipeline wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore(spec): add missing descriptions [cloud-security-posture-management] #3597

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .generator/schemas/v2/openapi.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44821,7 +44821,7 @@ components:
Protocol (OTLP) over gRPC and HTTP.


**Supported pipeline types:** logs, metrics'
**Supported pipeline types:** logs'
properties:
grpc_address_key:
description: Environment variable name containing the gRPC server address
Expand Down Expand Up @@ -44851,7 +44851,6 @@ components:
type: object
x-pipeline-types:
- logs
- metrics
ObservabilityPipelineOpentelemetrySourceType:
default: opentelemetry
description: The source type. The value should always be `opentelemetry`.
Expand Down Expand Up @@ -57419,6 +57418,7 @@ components:
- team:platform
- env:prod
items:
description: A tag associated with the security finding.
type: string
type: array
timestamp:
Expand Down
90 changes: 0 additions & 90 deletions examples/v2/observability-pipelines/ValidatePipeline_884022323.java
View file
Open in desktop

This file was deleted.

2 changes: 1 addition & 1 deletion src/main/java/com/datadog/api/client/v2/model/ObservabilityPipelineOpentelemetrySource.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@
* The <code>opentelemetry</code> source receives telemetry data using the OpenTelemetry Protocol
* (OTLP) over gRPC and HTTP.
*
* <p><strong>Supported pipeline types:</strong> logs, metrics
* <p><strong>Supported pipeline types:</strong> logs
*/
@JsonPropertyOrder({
ObservabilityPipelineOpentelemetrySource.JSON_PROPERTY_GRPC_ADDRESS_KEY,
Expand Down
1 change: 0 additions & 1 deletion ...tures/v2/Validate_a_metrics_pipeline_with_opentelemetry_source_returns_OK_response.freeze
View file
Open in desktop

This file was deleted.

32 changes: 0 additions & 32 deletions ...eatures/v2/Validate_a_metrics_pipeline_with_opentelemetry_source_returns_OK_response.json
View file
Open in desktop

This file was deleted.

8 changes: 0 additions & 8 deletions src/test/resources/com/datadog/api/client/v2/api/observability_pipelines.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,14 +149,6 @@ Feature: Observability Pipelines
And the response "data.attributes.config.destinations" has length 1
And the response "data.attributes.config.destinations[0].id" is equal to "updated-datadog-logs-destination-id"

@team:DataDog/observability-pipelines
Scenario: Validate a metrics pipeline with opentelemetry source returns "OK" response
Given new "ValidatePipeline" request
And body with value {"data": {"attributes": {"config": {"pipeline_type": "metrics", "destinations": [{"id": "datadog-metrics-destination", "inputs": ["my-processor-group"], "type": "datadog_metrics"}], "processor_groups": [{"enabled": true, "id": "my-processor-group", "include": "*", "inputs": ["opentelemetry-source"], "processors": [{"enabled": true, "id": "filter-processor", "include": "env:production", "type": "filter"}]}], "sources": [{"id": "opentelemetry-source", "type": "opentelemetry"}]}, "name": "Metrics OTel Pipeline"}, "type": "pipelines"}}
When the request is sent
Then the response status is 200 OK
And the response "errors" has length 0

@team:DataDog/observability-pipelines
Scenario: Validate an observability pipeline returns "Bad Request" response
Given new "ValidatePipeline" request
Expand Down
Loading