Skip to content
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.

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

feat(all): auto-regenerate discovery clients #1455

Merged
merged 1 commit into from Feb 24, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 6 additions & 2 deletions alertcenter/v1beta1/alertcenter-api.json
Expand Up @@ -423,7 +423,7 @@
}
}
},
"revision": "20220131",
"revision": "20220221",
"rootUrl": "https://alertcenter.googleapis.com/",
"schemas": {
"AccountSuspensionDetails": {
Expand Down Expand Up @@ -713,7 +713,7 @@
"type": "string"
},
"etag": {
"description": "Optional. `etag` is used for optimistic concurrency control as a way to help prevent simultaneous updates of an alert metadata from overwriting each other. It is strongly suggested that systems make use of the `etag` in the read-modify-write cycle to perform metatdata updates in order to avoid race conditions: An `etag` is returned in the response which contains alert metadata, and systems are expected to put that etag in the request to update alert metadata to ensure that their change will be applied to the same version of the alert metadata. If no `etag` is provided in the call to update alert metadata, then the existing alert metadata is overwritten blindly.",
"description": "Optional. `etag` is used for optimistic concurrency control as a way to help prevent simultaneous updates of an alert metadata from overwriting each other. It is strongly suggested that systems make use of the `etag` in the read-modify-write cycle to perform metadata updates in order to avoid race conditions: An `etag` is returned in the response which contains alert metadata, and systems are expected to put that etag in the request to update alert metadata to ensure that their change will be applied to the same version of the alert metadata. If no `etag` is provided in the call to update alert metadata, then the existing alert metadata is overwritten blindly.",
"type": "string"
},
"severity": {
Expand Down Expand Up @@ -1153,6 +1153,10 @@
"description": "A detailed, freeform incident description.",
"type": "string"
},
"domain": {
"description": "Customer domain for email template personalization.",
"type": "string"
},
"header": {
"description": "A header to display above the incident message. Typically used to attach a localized notice on the timeline for followup comms translations.",
"type": "string"
Expand Down
5 changes: 4 additions & 1 deletion alertcenter/v1beta1/alertcenter-gen.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

578 changes: 1 addition & 577 deletions analyticsadmin/v1alpha/analyticsadmin-api.json

Large diffs are not rendered by default.