Skip to content

Commit

Permalink
fix(cloudtrace): update the API
Browse files Browse the repository at this point in the history
#### cloudtrace:v2

The following keys were changed:
- schemas.Span.description
  • Loading branch information
yoshi-automation authored and sofisl committed Feb 9, 2023
1 parent 083c4d1 commit 07342c6
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions discovery/cloudtrace-v2.json
Expand Up @@ -181,7 +181,7 @@
}
}
},
"revision": "20230126",
"revision": "20230118",
"rootUrl": "https://cloudtrace.googleapis.com/",
"schemas": {
"Annotation": {
Expand Down Expand Up @@ -362,7 +362,7 @@
"type": "object"
},
"Span": {
"description": "A span represents a single operation within a trace. Spans can be nested to form a trace tree. Often, a trace contains a root span that describes the end-to-end latency, and one or more subspans for its sub-operations. A trace can also contain multiple root spans, or none at all. Spans do not need to be contiguous. There might be gaps or overlaps between spans in a trace.",
"description": "A span represents a single operation within a trace. Spans can be nested to form a trace tree. Often, a trace contains a root span that describes the end-to-end latency, and one or more subspans for its sub-operations. A trace can also contain multiple root spans, or none at all. Spans do not need to be contiguous—there might be gaps or overlaps between spans in a trace.",
"id": "Span",
"properties": {
"attributes": {
Expand Down
2 changes: 1 addition & 1 deletion src/apis/cloudtrace/v2.ts
Expand Up @@ -249,7 +249,7 @@ export namespace cloudtrace_v2 {
module?: Schema$TruncatableString;
}
/**
* A span represents a single operation within a trace. Spans can be nested to form a trace tree. Often, a trace contains a root span that describes the end-to-end latency, and one or more subspans for its sub-operations. A trace can also contain multiple root spans, or none at all. Spans do not need to be contiguous. There might be gaps or overlaps between spans in a trace.
* A span represents a single operation within a trace. Spans can be nested to form a trace tree. Often, a trace contains a root span that describes the end-to-end latency, and one or more subspans for its sub-operations. A trace can also contain multiple root spans, or none at all. Spans do not need to be contiguous—there might be gaps or overlaps between spans in a trace.
*/
export interface Schema$Span {
/**
Expand Down

0 comments on commit 07342c6

Please sign in to comment.