OMGeeky/google-apis-rs
1
0
Fork 0
mirror of https://github.com/OMGeeky/google-apis-rs.git synced 2026-02-23 15:49:49 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update documentation

Browse Source
This commit is contained in:
Sebastian Thiel
2022-03-08 15:36:16 +08:00
parent b84384c010
commit a20241b241
10471 changed files with 1934132 additions and 64947 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
google_pubsub1_cli/projects_subscriptions-modify-push-config/index.html
View File

@@ -5,7 +5,7 @@
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Subscriptions Modify Push Config - Pubsub v2.0.4+20210322</title>
<title>Subscriptions Modify Push Config - Pubsub v3.0.0+20220221</title>
@@ -34,7 +34,7 @@
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
<div class="wy-side-nav-search">
<a href=".." class="icon icon-home"> Pubsub v2.0.4+20210322</a>
<a href=".." class="icon icon-home"> Pubsub v3.0.0+20220221</a>
</div>
@@ -348,18 +348,18 @@ In the latter case it is advised to set the field-cursor to the data-structure's
<li>the value will be associated with the given <code>key</code></li>
</ul>
</li>
<li><code>oidc-token audience=et</code><ul>
<li><code>oidc-token audience=voluptua.</code><ul>
<li>Audience to be used when generating OIDC token. The audience claim identifies the recipients that the JWT is intended for. The audience value is a single case-sensitive string. Having multiple values (array) for the audience field is not supported. More info about the OIDC JWT token audience here: https://tools.ietf.org/html/rfc7519#section-4.1.3 Note: if not specified, the Push endpoint URL will be used.</li>
</ul>
</li>
<li>
<p><code>service-account-email=vero</code></p>
<p><code>service-account-email=amet.</code></p>
<ul>
<li><a href="https://cloud.google.com/iam/docs/service-accounts">Service account email</a> to be used for generating the OIDC token. The caller (for CreateSubscription, UpdateSubscription, and ModifyPushConfig RPCs) must have the iam.serviceAccounts.actAs permission for the service account.</li>
</ul>
</li>
<li>
<p><code>.. push-endpoint=erat</code></p>
<p><code>.. push-endpoint=consetetur</code></p>
<ul>
<li>A URL locating the endpoint to which messages should be pushed. For example, a Webhook endpoint might use <code>https://example.com/push</code>.</li>
</ul>