mirror of
https://github.com/OMGeeky/google-apis-rs.git
synced 2026-02-23 15:49:49 +01:00
Update documentation
This commit is contained in:
Sebastian Thiel
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Binary Authorization v2.0.4+20210318</title>
|
||||
<title>Binary Authorization v3.0.0+20220225</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"> Binary Authorization v2.0.4+20210318</a>
|
||||
<a href="." class="icon icon-home"> Binary Authorization v3.0.0+20220225</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -180,7 +180,7 @@ capabilities. Errors will be printed to standard error, and cause the program's
|
||||
|
||||
<p>Find the source code <a href="https://github.com/Byron/google-apis-rs/tree/main/gen/binaryauthorization1_beta1-cli">on github</a>.</p>
|
||||
<h1 id="usage">Usage</h1>
|
||||
<p>This documentation was generated from the <em>Binary Authorization</em> API at revision <em>20210318</em>. The CLI is at version <em>2.0.4</em>.</p>
|
||||
<p>This documentation was generated from the <em>Binary Authorization</em> API at revision <em>20220225</em>. The CLI is at version <em>3.0.0</em>.</p>
|
||||
<pre><code class="bash">binaryauthorization1-beta1 [options]
|
||||
projects
|
||||
attestors-create <parent> (-r <kv>)... [-p <v>]... [-o <out>]
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Attestors Create - Binary Authorization v2.0.4+20210318</title>
|
||||
<title>Attestors Create - Binary Authorization v3.0.0+20220225</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"> Binary Authorization v2.0.4+20210318</a>
|
||||
<a href=".." class="icon icon-home"> Binary Authorization v3.0.0+20220225</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -203,6 +203,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<p>For example, a structure like this:</p>
|
||||
<pre><code>Attestor:
|
||||
description: string
|
||||
etag: string
|
||||
name: string
|
||||
update-time: string
|
||||
user-owned-drydock-note:
|
||||
@@ -217,19 +218,23 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>Optional. A descriptive comment. This field may be updated. The field may be displayed in chooser dialogs.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>name=magna</code><ul>
|
||||
<li><code>etag=magna</code><ul>
|
||||
<li>Optional. Used to prevent updating the attestor when another request has updated it since it was retrieved.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>name=no</code><ul>
|
||||
<li>Required. The resource name, in the format: <code>projects/*/attestors/*</code>. This field may not be updated.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>update-time=no</code><ul>
|
||||
<li><code>update-time=ipsum</code><ul>
|
||||
<li>Output only. Time when the attestor was last updated.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>user-owned-drydock-note delegation-service-account-email=ipsum</code><ul>
|
||||
<li><code>user-owned-drydock-note delegation-service-account-email=voluptua.</code><ul>
|
||||
<li>Output only. This field will contain the service account email address that this Attestor will use as the principal when querying Container Analysis. Attestor administrators must grant this service account the IAM role needed to read attestations from the note_reference in Container Analysis (<code>containeranalysis.notes.occurrences.viewer</code>). This email address is fixed for the lifetime of the Attestor, but callers should not make any other assumptions about the service account email; future versions may use an email based on a different naming pattern.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>note-reference=voluptua.</code><ul>
|
||||
<li><code>note-reference=at</code><ul>
|
||||
<li>Required. The Drydock resource name of a ATTESTATION_AUTHORITY Note, created by the user, in the format: <code>projects/*/notes/*</code> (or the legacy <code>providers/*/notes/*</code>). This field may not be updated. An attestation by this attestor is stored as a Drydock ATTESTATION_AUTHORITY Occurrence that names a container image and that links to this Note. Drydock is an external dependency.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Attestors Delete - Binary Authorization v2.0.4+20210318</title>
|
||||
<title>Attestors Delete - Binary Authorization v3.0.0+20220225</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"> Binary Authorization v2.0.4+20210318</a>
|
||||
<a href=".." class="icon icon-home"> Binary Authorization v3.0.0+20220225</a>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Attestors Get Iam Policy - Binary Authorization v2.0.4+20210318</title>
|
||||
<title>Attestors Get Iam Policy - Binary Authorization v3.0.0+20220225</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"> Binary Authorization v2.0.4+20210318</a>
|
||||
<a href=".." class="icon icon-home"> Binary Authorization v3.0.0+20220225</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -209,7 +209,7 @@ or more key-value-pairs, and is called like this <code>-p k1=v1 k2=v2</code> eve
|
||||
<code>-p</code> for completeness.</p>
|
||||
<ul>
|
||||
<li><strong>-p options-requested-policy-version=integer</strong><ul>
|
||||
<li>Optional. The policy format version to be returned. Valid values are 0, 1, and 3. Requests specifying an invalid value will be rejected. Requests for policies with any conditional bindings must specify version 3. Policies without any conditional bindings may specify any valid value or leave the field unset. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
<li>Optional. The maximum policy version that will be used to format the policy. Valid values are 0, 1, and 3. Requests specifying an invalid value will be rejected. Requests for policies with any conditional role bindings must specify version 3. Policies with no conditional role bindings may specify any valid value or leave the field unset. The policy in the response might use the policy version that you specified, or it might use a lower policy version. For example, if you specify version 3, but the policy has no conditional role bindings, the response uses version 1. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Attestors Get - Binary Authorization v2.0.4+20210318</title>
|
||||
<title>Attestors Get - Binary Authorization v3.0.0+20220225</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"> Binary Authorization v2.0.4+20210318</a>
|
||||
<a href=".." class="icon icon-home"> Binary Authorization v3.0.0+20220225</a>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Attestors List - Binary Authorization v2.0.4+20210318</title>
|
||||
<title>Attestors List - Binary Authorization v3.0.0+20220225</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"> Binary Authorization v2.0.4+20210318</a>
|
||||
<a href=".." class="icon icon-home"> Binary Authorization v3.0.0+20220225</a>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Attestors Set Iam Policy - Binary Authorization v2.0.4+20210318</title>
|
||||
<title>Attestors Set Iam Policy - Binary Authorization v3.0.0+20220225</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"> Binary Authorization v2.0.4+20210318</a>
|
||||
<a href=".." class="icon icon-home"> Binary Authorization v3.0.0+20220225</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -207,11 +207,11 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .policy etag=at</code><ul>
|
||||
<li><code>-r .policy etag=sanctus</code><ul>
|
||||
<li><code>etag</code> is used for optimistic concurrency control as a way to help prevent simultaneous updates of a policy from overwriting each other. It is strongly suggested that systems make use of the <code>etag</code> in the read-modify-write cycle to perform policy updates in order to avoid race conditions: An <code>etag</code> is returned in the response to <code>getIamPolicy</code>, and systems are expected to put that etag in the request to <code>setIamPolicy</code> to ensure that their change will be applied to the same version of the policy. <strong>Important:</strong> If you use IAM Conditions, you must include the <code>etag</code> field whenever you call <code>setIamPolicy</code>. If you omit this field, then IAM allows you to overwrite a version <code>3</code> policy with a version <code>1</code> policy, and all of the conditions in the version <code>3</code> policy are lost.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>version=93</code><ul>
|
||||
<li><code>version=21</code><ul>
|
||||
<li>Specifies the format of the policy. Valid values are <code>0</code>, <code>1</code>, and <code>3</code>. Requests that specify an invalid value are rejected. Any operation that affects conditional role bindings must specify version <code>3</code>. This requirement applies to the following operations: * Getting a policy that includes a conditional role binding * Adding a conditional role binding to a policy * Changing a conditional role binding in a policy * Removing any role binding, with or without a condition, from a policy that includes conditions <strong>Important:</strong> If you use IAM Conditions, you must include the <code>etag</code> field whenever you call <code>setIamPolicy</code>. If you omit this field, then IAM allows you to overwrite a version <code>3</code> policy with a version <code>1</code> policy, and all of the conditions in the version <code>3</code> policy are lost. If a policy does not include any conditions, operations on that policy may specify any valid version or leave the field unset. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Attestors Test Iam Permissions - Binary Authorization v2.0.4+20210318</title>
|
||||
<title>Attestors Test Iam Permissions - Binary Authorization v3.0.0+20220225</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"> Binary Authorization v2.0.4+20210318</a>
|
||||
<a href=".." class="icon icon-home"> Binary Authorization v3.0.0+20220225</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -205,7 +205,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . permissions=sed</code><ul>
|
||||
<li><code>-r . permissions=amet.</code><ul>
|
||||
<li>The set of permissions to check for the <code>resource</code>. Permissions with wildcards (such as '<em>' or 'storage.</em>') are not allowed. For more information see <a href="https://cloud.google.com/iam/docs/overview#permissions">IAM Overview</a>.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Attestors Update - Binary Authorization v2.0.4+20210318</title>
|
||||
<title>Attestors Update - Binary Authorization v3.0.0+20220225</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"> Binary Authorization v2.0.4+20210318</a>
|
||||
<a href=".." class="icon icon-home"> Binary Authorization v3.0.0+20220225</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -200,6 +200,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<p>For example, a structure like this:</p>
|
||||
<pre><code>Attestor:
|
||||
description: string
|
||||
etag: string
|
||||
name: string
|
||||
update-time: string
|
||||
user-owned-drydock-note:
|
||||
@@ -210,23 +211,27 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . description=amet.</code><ul>
|
||||
<li><code>-r . description=takimata</code><ul>
|
||||
<li>Optional. A descriptive comment. This field may be updated. The field may be displayed in chooser dialogs.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>name=takimata</code><ul>
|
||||
<li><code>etag=amet.</code><ul>
|
||||
<li>Optional. Used to prevent updating the attestor when another request has updated it since it was retrieved.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>name=duo</code><ul>
|
||||
<li>Required. The resource name, in the format: <code>projects/*/attestors/*</code>. This field may not be updated.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>update-time=amet.</code><ul>
|
||||
<li><code>update-time=ipsum</code><ul>
|
||||
<li>Output only. Time when the attestor was last updated.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>user-owned-drydock-note delegation-service-account-email=duo</code><ul>
|
||||
<li><code>user-owned-drydock-note delegation-service-account-email=gubergren</code><ul>
|
||||
<li>Output only. This field will contain the service account email address that this Attestor will use as the principal when querying Container Analysis. Attestor administrators must grant this service account the IAM role needed to read attestations from the note_reference in Container Analysis (<code>containeranalysis.notes.occurrences.viewer</code>). This email address is fixed for the lifetime of the Attestor, but callers should not make any other assumptions about the service account email; future versions may use an email based on a different naming pattern.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>note-reference=ipsum</code><ul>
|
||||
<li><code>note-reference=lorem</code><ul>
|
||||
<li>Required. The Drydock resource name of a ATTESTATION_AUTHORITY Note, created by the user, in the format: <code>projects/*/notes/*</code> (or the legacy <code>providers/*/notes/*</code>). This field may not be updated. An attestation by this attestor is stored as a Drydock ATTESTATION_AUTHORITY Occurrence that names a container image and that links to this Note. Drydock is an external dependency.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Attestors Validate Attestation Occurrence - Binary Authorization v2.0.4+20210318</title>
|
||||
<title>Attestors Validate Attestation Occurrence - Binary Authorization v3.0.0+20220225</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"> Binary Authorization v2.0.4+20210318</a>
|
||||
<a href=".." class="icon icon-home"> Binary Authorization v3.0.0+20220225</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -215,12 +215,12 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. occurrence-note=lorem</code></p>
|
||||
<p><code>.. occurrence-note=eos</code></p>
|
||||
<ul>
|
||||
<li>Required. The resource name of the Note to which the containing Occurrence is associated.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>occurrence-resource-uri=gubergren</code><ul>
|
||||
<li><code>occurrence-resource-uri=dolor</code><ul>
|
||||
<li>Required. The URI of the artifact (e.g. container image) that is the subject of the containing Occurrence.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Get Policy - Binary Authorization v2.0.4+20210318</title>
|
||||
<title>Get Policy - Binary Authorization v3.0.0+20220225</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"> Binary Authorization v2.0.4+20210318</a>
|
||||
<a href=".." class="icon icon-home"> Binary Authorization v3.0.0+20220225</a>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Policy Get Iam Policy - Binary Authorization v2.0.4+20210318</title>
|
||||
<title>Policy Get Iam Policy - Binary Authorization v3.0.0+20220225</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"> Binary Authorization v2.0.4+20210318</a>
|
||||
<a href=".." class="icon icon-home"> Binary Authorization v3.0.0+20220225</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -209,7 +209,7 @@ or more key-value-pairs, and is called like this <code>-p k1=v1 k2=v2</code> eve
|
||||
<code>-p</code> for completeness.</p>
|
||||
<ul>
|
||||
<li><strong>-p options-requested-policy-version=integer</strong><ul>
|
||||
<li>Optional. The policy format version to be returned. Valid values are 0, 1, and 3. Requests specifying an invalid value will be rejected. Requests for policies with any conditional bindings must specify version 3. Policies without any conditional bindings may specify any valid value or leave the field unset. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
<li>Optional. The maximum policy version that will be used to format the policy. Valid values are 0, 1, and 3. Requests specifying an invalid value will be rejected. Requests for policies with any conditional role bindings must specify version 3. Policies with no conditional role bindings may specify any valid value or leave the field unset. The policy in the response might use the policy version that you specified, or it might use a lower policy version. For example, if you specify version 3, but the policy has no conditional role bindings, the response uses version 1. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Policy Set Iam Policy - Binary Authorization v2.0.4+20210318</title>
|
||||
<title>Policy Set Iam Policy - Binary Authorization v3.0.0+20220225</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"> Binary Authorization v2.0.4+20210318</a>
|
||||
<a href=".." class="icon icon-home"> Binary Authorization v3.0.0+20220225</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -207,11 +207,11 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .policy etag=eos</code><ul>
|
||||
<li><code>-r .policy etag=ea</code><ul>
|
||||
<li><code>etag</code> is used for optimistic concurrency control as a way to help prevent simultaneous updates of a policy from overwriting each other. It is strongly suggested that systems make use of the <code>etag</code> in the read-modify-write cycle to perform policy updates in order to avoid race conditions: An <code>etag</code> is returned in the response to <code>getIamPolicy</code>, and systems are expected to put that etag in the request to <code>setIamPolicy</code> to ensure that their change will be applied to the same version of the policy. <strong>Important:</strong> If you use IAM Conditions, you must include the <code>etag</code> field whenever you call <code>setIamPolicy</code>. If you omit this field, then IAM allows you to overwrite a version <code>3</code> policy with a version <code>1</code> policy, and all of the conditions in the version <code>3</code> policy are lost.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>version=97</code><ul>
|
||||
<li><code>version=46</code><ul>
|
||||
<li>Specifies the format of the policy. Valid values are <code>0</code>, <code>1</code>, and <code>3</code>. Requests that specify an invalid value are rejected. Any operation that affects conditional role bindings must specify version <code>3</code>. This requirement applies to the following operations: * Getting a policy that includes a conditional role binding * Adding a conditional role binding to a policy * Changing a conditional role binding in a policy * Removing any role binding, with or without a condition, from a policy that includes conditions <strong>Important:</strong> If you use IAM Conditions, you must include the <code>etag</code> field whenever you call <code>setIamPolicy</code>. If you omit this field, then IAM allows you to overwrite a version <code>3</code> policy with a version <code>1</code> policy, and all of the conditions in the version <code>3</code> policy are lost. If a policy does not include any conditions, operations on that policy may specify any valid version or leave the field unset. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Policy Test Iam Permissions - Binary Authorization v2.0.4+20210318</title>
|
||||
<title>Policy Test Iam Permissions - Binary Authorization v3.0.0+20220225</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"> Binary Authorization v2.0.4+20210318</a>
|
||||
<a href=".." class="icon icon-home"> Binary Authorization v3.0.0+20220225</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -205,7 +205,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . permissions=ea</code><ul>
|
||||
<li><code>-r . permissions=invidunt</code><ul>
|
||||
<li>The set of permissions to check for the <code>resource</code>. Permissions with wildcards (such as '<em>' or 'storage.</em>') are not allowed. For more information see <a href="https://cloud.google.com/iam/docs/overview#permissions">IAM Overview</a>.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Update Policy - Binary Authorization v2.0.4+20210318</title>
|
||||
<title>Update Policy - Binary Authorization v3.0.0+20220225</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"> Binary Authorization v2.0.4+20210318</a>
|
||||
<a href=".." class="icon icon-home"> Binary Authorization v3.0.0+20220225</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -204,6 +204,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
evaluation-mode: string
|
||||
require-attestations-by: [string]
|
||||
description: string
|
||||
etag: string
|
||||
global-policy-evaluation-mode: string
|
||||
name: string
|
||||
update-time: string
|
||||
@@ -212,36 +213,40 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .default-admission-rule enforcement-mode=ipsum</code><ul>
|
||||
<li><code>-r .default-admission-rule enforcement-mode=amet</code><ul>
|
||||
<li>Required. The action when a pod creation is denied by the admission rule.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>evaluation-mode=invidunt</code><ul>
|
||||
<li><code>evaluation-mode=duo</code><ul>
|
||||
<li>Required. How this admission rule will be evaluated.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>require-attestations-by=amet</code></p>
|
||||
<p><code>require-attestations-by=ipsum</code></p>
|
||||
<ul>
|
||||
<li>Optional. The resource names of the attestors that must attest to a container image, in the format <code>projects/*/attestors/*</code>. Each attestor must exist before a policy can reference it. To add an attestor to a policy the principal issuing the policy change request must be able to read the attestor resource. Note: this field must be non-empty when the evaluation_mode field specifies REQUIRE_ATTESTATION, otherwise it must be empty.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. description=duo</code></p>
|
||||
<p><code>.. description=sed</code></p>
|
||||
<ul>
|
||||
<li>Optional. A descriptive comment.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>global-policy-evaluation-mode=ipsum</code><ul>
|
||||
<li><code>etag=ut</code><ul>
|
||||
<li>Optional. Used to prevent updating the policy when another request has updated it since it was retrieved.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>global-policy-evaluation-mode=gubergren</code><ul>
|
||||
<li>Optional. Controls the evaluation of a Google-maintained global admission policy for common system-level images. Images not covered by the global policy will be subject to the project admission policy. This setting has no effect when specified inside a global admission policy.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>name=sed</code><ul>
|
||||
<li><code>name=rebum.</code><ul>
|
||||
<li>Output only. The resource name, in the format <code>projects/*/policy</code>. There is at most one policy per project.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>update-time=ut</code><ul>
|
||||
<li><code>update-time=est</code><ul>
|
||||
<li>Output only. Time when the policy was last updated.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Get Policy - Binary Authorization v2.0.4+20210318</title>
|
||||
<title>Get Policy - Binary Authorization v3.0.0+20220225</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"> Binary Authorization v2.0.4+20210318</a>
|
||||
<a href=".." class="icon icon-home"> Binary Authorization v3.0.0+20220225</a>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user