blob: 9d5256cc086b8ecd19fbfda33022ae9a6a8da18c [file] [log] [blame]
Bu Sun Kim715bd7f2019-06-14 16:50:42 -07001<html><body>
2<style>
3
4body, h1, h2, h3, div, span, p, pre, a {
5 margin: 0;
6 padding: 0;
7 border: 0;
8 font-weight: inherit;
9 font-style: inherit;
10 font-size: 100%;
11 font-family: inherit;
12 vertical-align: baseline;
13}
14
15body {
16 font-size: 13px;
17 padding: 1em;
18}
19
20h1 {
21 font-size: 26px;
22 margin-bottom: 1em;
23}
24
25h2 {
26 font-size: 24px;
27 margin-bottom: 1em;
28}
29
30h3 {
31 font-size: 20px;
32 margin-bottom: 1em;
33 margin-top: 1em;
34}
35
36pre, code {
37 line-height: 1.5;
38 font-family: Monaco, 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', 'Lucida Console', monospace;
39}
40
41pre {
42 margin-top: 0.5em;
43}
44
45h1, h2, h3, p {
46 font-family: Arial, sans serif;
47}
48
49h1, h2, h3 {
50 border-bottom: solid #CCC 1px;
51}
52
53.toc_element {
54 margin-top: 0.5em;
55}
56
57.firstline {
58 margin-left: 2 em;
59}
60
61.method {
62 margin-top: 1em;
63 border: solid 1px #CCC;
64 padding: 1em;
65 background: #EEE;
66}
67
68.details {
69 font-weight: bold;
70 font-size: 14px;
71}
72
73</style>
74
75<h1><a href="containeranalysis_v1alpha1.html">Container Analysis API</a> . <a href="containeranalysis_v1alpha1.projects.html">projects</a> . <a href="containeranalysis_v1alpha1.projects.notes.html">notes</a></h1>
76<h2>Instance Methods</h2>
77<p class="toc_element">
78 <code><a href="containeranalysis_v1alpha1.projects.notes.occurrences.html">occurrences()</a></code>
79</p>
80<p class="firstline">Returns the occurrences Resource.</p>
81
82<p class="toc_element">
Dmitry Frenkel3e17f892020-10-06 16:46:05 -070083 <code><a href="#close">close()</a></code></p>
84<p class="firstline">Close httplib2 connections.</p>
85<p class="toc_element">
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -080086 <code><a href="#create">create(parent, body=None, name=None, noteId=None, x__xgafv=None)</a></code></p>
Bu Sun Kim715bd7f2019-06-14 16:50:42 -070087<p class="firstline">Creates a new `Note`.</p>
88<p class="toc_element">
89 <code><a href="#delete">delete(name, x__xgafv=None)</a></code></p>
90<p class="firstline">Deletes the given `Note` from the system.</p>
91<p class="toc_element">
92 <code><a href="#get">get(name, x__xgafv=None)</a></code></p>
93<p class="firstline">Returns the requested `Note`.</p>
94<p class="toc_element">
95 <code><a href="#getIamPolicy">getIamPolicy(resource, body=None, x__xgafv=None)</a></code></p>
Dmitry Frenkel3e17f892020-10-06 16:46:05 -070096<p class="firstline">Gets the access control policy for a note or an `Occurrence` resource. Requires `containeranalysis.notes.setIamPolicy` or `containeranalysis.occurrences.setIamPolicy` permission if the resource is a note or occurrence, respectively. Attempting to call this method on a resource without the required permission will result in a `PERMISSION_DENIED` error. Attempting to call this method on a non-existent resource will result in a `NOT_FOUND` error if the user has list permission on the project, or a `PERMISSION_DENIED` error otherwise. The resource takes the following formats: `projects/{PROJECT_ID}/occurrences/{OCCURRENCE_ID}` for occurrences and projects/{PROJECT_ID}/notes/{NOTE_ID} for notes</p>
Bu Sun Kim715bd7f2019-06-14 16:50:42 -070097<p class="toc_element">
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -080098 <code><a href="#list">list(parent, filter=None, name=None, pageSize=None, pageToken=None, x__xgafv=None)</a></code></p>
Bu Sun Kim715bd7f2019-06-14 16:50:42 -070099<p class="firstline">Lists all `Notes` for a given project.</p>
100<p class="toc_element">
101 <code><a href="#list_next">list_next(previous_request, previous_response)</a></code></p>
102<p class="firstline">Retrieves the next page of results.</p>
103<p class="toc_element">
Dan O'Mearadd494642020-05-01 07:42:23 -0700104 <code><a href="#patch">patch(name, body=None, updateMask=None, x__xgafv=None)</a></code></p>
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700105<p class="firstline">Updates an existing `Note`.</p>
106<p class="toc_element">
Dan O'Mearadd494642020-05-01 07:42:23 -0700107 <code><a href="#setIamPolicy">setIamPolicy(resource, body=None, x__xgafv=None)</a></code></p>
Dmitry Frenkel3e17f892020-10-06 16:46:05 -0700108<p class="firstline">Sets the access control policy on the specified `Note` or `Occurrence`. Requires `containeranalysis.notes.setIamPolicy` or `containeranalysis.occurrences.setIamPolicy` permission if the resource is a `Note` or an `Occurrence`, respectively. Attempting to call this method without these permissions will result in a ` `PERMISSION_DENIED` error. Attempting to call this method on a non-existent resource will result in a `NOT_FOUND` error if the user has `containeranalysis.notes.list` permission on a `Note` or `containeranalysis.occurrences.list` on an `Occurrence`, or a `PERMISSION_DENIED` error otherwise. The resource takes the following formats: `projects/{projectid}/occurrences/{occurrenceid}` for occurrences and projects/{projectid}/notes/{noteid} for notes</p>
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700109<p class="toc_element">
Dan O'Mearadd494642020-05-01 07:42:23 -0700110 <code><a href="#testIamPermissions">testIamPermissions(resource, body=None, x__xgafv=None)</a></code></p>
Dmitry Frenkel3e17f892020-10-06 16:46:05 -0700111<p class="firstline">Returns the permissions that a caller has on the specified note or occurrence resource. Requires list permission on the project (for example, "storage.objects.list" on the containing bucket for testing permission of an object). Attempting to call this method on a non-existent resource will result in a `NOT_FOUND` error if the user has list permission on the project, or a `PERMISSION_DENIED` error otherwise. The resource takes the following formats: `projects/{PROJECT_ID}/occurrences/{OCCURRENCE_ID}` for `Occurrences` and `projects/{PROJECT_ID}/notes/{NOTE_ID}` for `Notes`</p>
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700112<h3>Method Details</h3>
113<div class="method">
Dmitry Frenkel3e17f892020-10-06 16:46:05 -0700114 <code class="details" id="close">close()</code>
115 <pre>Close httplib2 connections.</pre>
116</div>
117
118<div class="method">
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800119 <code class="details" id="create">create(parent, body=None, name=None, noteId=None, x__xgafv=None)</code>
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700120 <pre>Creates a new `Note`.
121
122Args:
Dmitry Frenkel3e17f892020-10-06 16:46:05 -0700123 parent: string, This field contains the project Id for example: &quot;projects/{project_id} (required)
Dan O'Mearadd494642020-05-01 07:42:23 -0700124 body: object, The request body.
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700125 The object takes the form of:
126
127{ # Provides a detailed description of a `Note`.
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800128 &quot;attestationAuthority&quot;: { # Note kind that represents a logical attestation &quot;role&quot; or &quot;authority&quot;. For example, an organization might have one `AttestationAuthority` for &quot;QA&quot; and one for &quot;build&quot;. This Note is intended to act strictly as a grouping mechanism for the attached Occurrences (Attestations). This grouping mechanism also provides a security boundary, since IAM ACLs gate the ability for a principle to attach an Occurrence to a given Note. It also provides a single point of lookup to find all attached Attestation Occurrences, even if they don&#x27;t all live in the same project. # A note describing an attestation role.
129 &quot;hint&quot;: { # This submessage provides human-readable hints about the purpose of the AttestationAuthority. Because the name of a Note acts as its resource reference, it is important to disambiguate the canonical name of the Note (which might be a UUID for security purposes) from &quot;readable&quot; names more suitable for debug output. Note that these hints should NOT be used to look up AttestationAuthorities in security sensitive contexts, such as when looking up Attestations to verify.
130 &quot;humanReadableName&quot;: &quot;A String&quot;, # The human readable name of this Attestation Authority, for example &quot;qa&quot;.
Bu Sun Kim673ec5c2020-11-16 11:05:03 -0700131 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800132 },
133 &quot;baseImage&quot;: { # Basis describes the base image portion (Note) of the DockerImage relationship. Linked occurrences are derived from this or an equivalent image via: FROM Or an equivalent reference, e.g. a tag of the resource_url. # A note describing a base image.
134 &quot;fingerprint&quot;: { # A set of properties that uniquely identify a given Docker image. # The fingerprint of the base image.
135 &quot;v1Name&quot;: &quot;A String&quot;, # The layer-id of the final layer in the Docker image&#x27;s v1 representation. This field can be used as a filter in list requests.
136 &quot;v2Blob&quot;: [ # The ordered list of v2 blobs that represent a given image.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800137 &quot;A String&quot;,
138 ],
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800139 &quot;v2Name&quot;: &quot;A String&quot;, # Output only. The name of the image&#x27;s v2 blobs computed via: [bottom] := v2_blobbottom := sha256(v2_blob[N] + &quot; &quot; + v2_name[N+1]) Only the name of the final blob is kept. This field can be used as a filter in list requests.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800140 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800141 &quot;resourceUrl&quot;: &quot;A String&quot;, # The resource_url for the resource representing the basis of associated occurrence images.
142 },
143 &quot;buildType&quot;: { # Note holding the version of the provider&#x27;s builder and the signature of the provenance message in linked BuildDetails. # Build provenance type for a verifiable build.
144 &quot;builderVersion&quot;: &quot;A String&quot;, # Version of the builder which produced this Note.
145 &quot;signature&quot;: { # Message encapsulating the signature of the verified build. # Signature of the build in Occurrences pointing to the Note containing this `BuilderDetails`.
146 &quot;keyId&quot;: &quot;A String&quot;, # An Id for the key used to sign. This could be either an Id for the key stored in `public_key` (such as the Id or fingerprint for a PGP key, or the CN for a cert), or a reference to an external key (such as a reference to a key in Cloud Key Management Service).
147 &quot;keyType&quot;: &quot;A String&quot;, # The type of the key, either stored in `public_key` or referenced in `key_id`
148 &quot;publicKey&quot;: &quot;A String&quot;, # Public key of the builder which can be used to verify that the related findings are valid and unchanged. If `key_type` is empty, this defaults to PEM encoded public keys. This field may be empty if `key_id` references an external key. For Cloud Build based signatures, this is a PEM encoded public key. To verify the Cloud Build signature, place the contents of this field into a file (public.pem). The signature field is base64-decoded into its binary representation in signature.bin, and the provenance bytes from `BuildDetails` are base64-decoded into a binary representation in signed.bin. OpenSSL can then verify the signature: `openssl sha256 -verify public.pem -signature signature.bin signed.bin`
149 &quot;signature&quot;: &quot;A String&quot;, # Signature of the related `BuildProvenance`, encoded in a base64 string.
150 },
151 },
152 &quot;createTime&quot;: &quot;A String&quot;, # Output only. The time this note was created. This field can be used as a filter in list requests.
153 &quot;deployable&quot;: { # An artifact that can be deployed in some runtime. # A note describing something that can be deployed.
154 &quot;resourceUri&quot;: [ # Resource URI for the artifact being deployed.
155 &quot;A String&quot;,
156 ],
157 },
158 &quot;discovery&quot;: { # A note that indicates a type of analysis a provider would perform. This note exists in a provider&#x27;s project. A `Discovery` occurrence is created in a consumer&#x27;s project at the start of analysis. The occurrence&#x27;s operation will indicate the status of the analysis. Absence of an occurrence linked to this note for a resource indicates that analysis hasn&#x27;t started. # A note describing a provider/analysis type.
159 &quot;analysisKind&quot;: &quot;A String&quot;, # The kind of analysis that is handled by this discovery.
160 },
161 &quot;expirationTime&quot;: &quot;A String&quot;, # Time of expiration for this note, null if note does not expire.
162 &quot;kind&quot;: &quot;A String&quot;, # Output only. This explicitly denotes which kind of note is specified. This field can be used as a filter in list requests.
163 &quot;longDescription&quot;: &quot;A String&quot;, # A detailed description of this `Note`.
164 &quot;name&quot;: &quot;A String&quot;, # The name of the note in the form &quot;projects/{provider_project_id}/notes/{NOTE_ID}&quot;
165 &quot;package&quot;: { # This represents a particular package that is distributed over various channels. e.g. glibc (aka libc6) is distributed by many, at various versions. # A note describing a package hosted by various package managers.
166 &quot;distribution&quot;: [ # The various channels by which a package is distributed.
167 { # This represents a particular channel of distribution for a given package. e.g. Debian&#x27;s jessie-backports dpkg mirror
168 &quot;architecture&quot;: &quot;A String&quot;, # The CPU architecture for which packages in this distribution channel were built
169 &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format](https://cpe.mitre.org/specification/) denoting the package manager version distributing a package.
170 &quot;description&quot;: &quot;A String&quot;, # The distribution channel-specific description of this package.
171 &quot;latestVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The latest available version of this package in this distribution channel.
172 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800173 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800174 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
175 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
176 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
177 },
178 &quot;maintainer&quot;: &quot;A String&quot;, # A freeform string denoting the maintainer of this package.
179 &quot;url&quot;: &quot;A String&quot;, # The distribution channel-specific homepage for this package.
180 },
181 ],
182 &quot;name&quot;: &quot;A String&quot;, # The name of the package.
183 },
184 &quot;relatedUrl&quot;: [ # URLs associated with this note
185 { # Metadata for any related URL information
186 &quot;label&quot;: &quot;A String&quot;, # Label to describe usage of the URL
187 &quot;url&quot;: &quot;A String&quot;, # Specific URL to associate with the note
188 },
189 ],
190 &quot;shortDescription&quot;: &quot;A String&quot;, # A one sentence description of this `Note`.
191 &quot;updateTime&quot;: &quot;A String&quot;, # Output only. The time this note was last updated. This field can be used as a filter in list requests.
192 &quot;upgrade&quot;: { # An Upgrade Note represents a potential upgrade of a package to a given version. For each package version combination (i.e. bash 4.0, bash 4.1, bash 4.1.2), there will be a Upgrade Note. # A note describing an upgrade.
193 &quot;distributions&quot;: [ # Metadata about the upgrade for each specific operating system.
194 { # The Upgrade Distribution represents metadata about the Upgrade for each operating system (CPE). Some distributions have additional metadata around updates, classifying them into various categories and severities.
195 &quot;classification&quot;: &quot;A String&quot;, # The operating system classification of this Upgrade, as specified by the upstream operating system upgrade feed.
196 &quot;cpeUri&quot;: &quot;A String&quot;, # Required - The specific operating system this metadata applies to. See https://cpe.mitre.org/specification/.
197 &quot;cve&quot;: [ # The cve that would be resolved by this upgrade.
198 &quot;A String&quot;,
199 ],
200 &quot;severity&quot;: &quot;A String&quot;, # The severity as specified by the upstream operating system.
201 },
202 ],
203 &quot;package&quot;: &quot;A String&quot;, # Required - The package this Upgrade is for.
204 &quot;version&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # Required - The version of the package in machine + human readable form.
205 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800206 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800207 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
208 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
209 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
210 },
211 },
212 &quot;vulnerabilityType&quot;: { # VulnerabilityType provides metadata about a security vulnerability. # A package vulnerability type of note.
213 &quot;cvssScore&quot;: 3.14, # The CVSS score for this Vulnerability.
214 &quot;details&quot;: [ # All information about the package to specifically identify this vulnerability. One entry per (version range and cpe_uri) the package vulnerability has manifested in.
215 { # Identifies all occurrences of this vulnerability in the package for a specific distro/location For example: glibc in cpe:/o:debian:debian_linux:8 for versions 2.1 - 2.2
216 &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format] (https://cpe.mitre.org/specification/) in which the vulnerability manifests. Examples include distro or storage location for vulnerable jar. This field can be used as a filter in list requests.
217 &quot;description&quot;: &quot;A String&quot;, # A vendor-specific description of this note.
218 &quot;fixedLocation&quot;: { # The location of the vulnerability # The fix for this specific package version.
219 &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format] (https://cpe.mitre.org/specification/) format. Examples include distro or storage location for vulnerable jar. This field can be used as a filter in list requests.
220 &quot;package&quot;: &quot;A String&quot;, # The package being described.
221 &quot;version&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The version of the package being described. This field can be used as a filter in list requests.
Yoshi Automation Botb6971b02020-11-26 17:16:03 -0800222 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800223 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botb6971b02020-11-26 17:16:03 -0800224 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800225 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800226 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
227 },
Yoshi Automation Botb6971b02020-11-26 17:16:03 -0800228 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800229 &quot;isObsolete&quot;: True or False, # Whether this Detail is obsolete. Occurrences are expected not to point to obsolete details.
230 &quot;maxAffectedVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The max version of the package in which the vulnerability exists.
231 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800232 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800233 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
234 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
235 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
236 },
237 &quot;minAffectedVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The min version of the package in which the vulnerability exists.
238 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800239 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800240 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
241 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
242 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
243 },
244 &quot;package&quot;: &quot;A String&quot;, # The name of the package where the vulnerability was found. This field can be used as a filter in list requests.
245 &quot;packageType&quot;: &quot;A String&quot;, # The type of package; whether native or non native(ruby gems, node.js packages etc)
246 &quot;severityName&quot;: &quot;A String&quot;, # The severity (eg: distro assigned severity) for this vulnerability.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800247 &quot;source&quot;: &quot;A String&quot;, # The source from which the information in this Detail was obtained.
Yoshi Automation Bot0d561ef2020-11-25 07:50:41 -0800248 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800249 ],
250 &quot;severity&quot;: &quot;A String&quot;, # Note provider assigned impact of the vulnerability
251 },
252}
Bu Sun Kimd059ad82020-07-22 17:02:09 -0700253
Yoshi Automation Botb6971b02020-11-26 17:16:03 -0800254 name: string, The name of the project. Should be of the form &quot;providers/{provider_id}&quot;. @Deprecated
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800255 noteId: string, The ID to use for this note.
Bu Sun Kimd059ad82020-07-22 17:02:09 -0700256 x__xgafv: string, V1 error format.
257 Allowed values
258 1 - v1 error format
259 2 - v2 error format
260
261Returns:
262 An object of the form:
263
264 { # Provides a detailed description of a `Note`.
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800265 &quot;attestationAuthority&quot;: { # Note kind that represents a logical attestation &quot;role&quot; or &quot;authority&quot;. For example, an organization might have one `AttestationAuthority` for &quot;QA&quot; and one for &quot;build&quot;. This Note is intended to act strictly as a grouping mechanism for the attached Occurrences (Attestations). This grouping mechanism also provides a security boundary, since IAM ACLs gate the ability for a principle to attach an Occurrence to a given Note. It also provides a single point of lookup to find all attached Attestation Occurrences, even if they don&#x27;t all live in the same project. # A note describing an attestation role.
266 &quot;hint&quot;: { # This submessage provides human-readable hints about the purpose of the AttestationAuthority. Because the name of a Note acts as its resource reference, it is important to disambiguate the canonical name of the Note (which might be a UUID for security purposes) from &quot;readable&quot; names more suitable for debug output. Note that these hints should NOT be used to look up AttestationAuthorities in security sensitive contexts, such as when looking up Attestations to verify.
267 &quot;humanReadableName&quot;: &quot;A String&quot;, # The human readable name of this Attestation Authority, for example &quot;qa&quot;.
268 },
269 },
270 &quot;baseImage&quot;: { # Basis describes the base image portion (Note) of the DockerImage relationship. Linked occurrences are derived from this or an equivalent image via: FROM Or an equivalent reference, e.g. a tag of the resource_url. # A note describing a base image.
271 &quot;fingerprint&quot;: { # A set of properties that uniquely identify a given Docker image. # The fingerprint of the base image.
272 &quot;v1Name&quot;: &quot;A String&quot;, # The layer-id of the final layer in the Docker image&#x27;s v1 representation. This field can be used as a filter in list requests.
273 &quot;v2Blob&quot;: [ # The ordered list of v2 blobs that represent a given image.
274 &quot;A String&quot;,
275 ],
276 &quot;v2Name&quot;: &quot;A String&quot;, # Output only. The name of the image&#x27;s v2 blobs computed via: [bottom] := v2_blobbottom := sha256(v2_blob[N] + &quot; &quot; + v2_name[N+1]) Only the name of the final blob is kept. This field can be used as a filter in list requests.
277 },
278 &quot;resourceUrl&quot;: &quot;A String&quot;, # The resource_url for the resource representing the basis of associated occurrence images.
279 },
280 &quot;buildType&quot;: { # Note holding the version of the provider&#x27;s builder and the signature of the provenance message in linked BuildDetails. # Build provenance type for a verifiable build.
281 &quot;builderVersion&quot;: &quot;A String&quot;, # Version of the builder which produced this Note.
282 &quot;signature&quot;: { # Message encapsulating the signature of the verified build. # Signature of the build in Occurrences pointing to the Note containing this `BuilderDetails`.
283 &quot;keyId&quot;: &quot;A String&quot;, # An Id for the key used to sign. This could be either an Id for the key stored in `public_key` (such as the Id or fingerprint for a PGP key, or the CN for a cert), or a reference to an external key (such as a reference to a key in Cloud Key Management Service).
284 &quot;keyType&quot;: &quot;A String&quot;, # The type of the key, either stored in `public_key` or referenced in `key_id`
285 &quot;publicKey&quot;: &quot;A String&quot;, # Public key of the builder which can be used to verify that the related findings are valid and unchanged. If `key_type` is empty, this defaults to PEM encoded public keys. This field may be empty if `key_id` references an external key. For Cloud Build based signatures, this is a PEM encoded public key. To verify the Cloud Build signature, place the contents of this field into a file (public.pem). The signature field is base64-decoded into its binary representation in signature.bin, and the provenance bytes from `BuildDetails` are base64-decoded into a binary representation in signed.bin. OpenSSL can then verify the signature: `openssl sha256 -verify public.pem -signature signature.bin signed.bin`
286 &quot;signature&quot;: &quot;A String&quot;, # Signature of the related `BuildProvenance`, encoded in a base64 string.
287 },
288 },
289 &quot;createTime&quot;: &quot;A String&quot;, # Output only. The time this note was created. This field can be used as a filter in list requests.
290 &quot;deployable&quot;: { # An artifact that can be deployed in some runtime. # A note describing something that can be deployed.
291 &quot;resourceUri&quot;: [ # Resource URI for the artifact being deployed.
292 &quot;A String&quot;,
293 ],
294 },
295 &quot;discovery&quot;: { # A note that indicates a type of analysis a provider would perform. This note exists in a provider&#x27;s project. A `Discovery` occurrence is created in a consumer&#x27;s project at the start of analysis. The occurrence&#x27;s operation will indicate the status of the analysis. Absence of an occurrence linked to this note for a resource indicates that analysis hasn&#x27;t started. # A note describing a provider/analysis type.
296 &quot;analysisKind&quot;: &quot;A String&quot;, # The kind of analysis that is handled by this discovery.
297 },
298 &quot;expirationTime&quot;: &quot;A String&quot;, # Time of expiration for this note, null if note does not expire.
299 &quot;kind&quot;: &quot;A String&quot;, # Output only. This explicitly denotes which kind of note is specified. This field can be used as a filter in list requests.
300 &quot;longDescription&quot;: &quot;A String&quot;, # A detailed description of this `Note`.
301 &quot;name&quot;: &quot;A String&quot;, # The name of the note in the form &quot;projects/{provider_project_id}/notes/{NOTE_ID}&quot;
302 &quot;package&quot;: { # This represents a particular package that is distributed over various channels. e.g. glibc (aka libc6) is distributed by many, at various versions. # A note describing a package hosted by various package managers.
303 &quot;distribution&quot;: [ # The various channels by which a package is distributed.
304 { # This represents a particular channel of distribution for a given package. e.g. Debian&#x27;s jessie-backports dpkg mirror
305 &quot;architecture&quot;: &quot;A String&quot;, # The CPU architecture for which packages in this distribution channel were built
306 &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format](https://cpe.mitre.org/specification/) denoting the package manager version distributing a package.
307 &quot;description&quot;: &quot;A String&quot;, # The distribution channel-specific description of this package.
308 &quot;latestVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The latest available version of this package in this distribution channel.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800309 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800310 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800311 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800312 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800313 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
314 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800315 &quot;maintainer&quot;: &quot;A String&quot;, # A freeform string denoting the maintainer of this package.
316 &quot;url&quot;: &quot;A String&quot;, # The distribution channel-specific homepage for this package.
Yoshi Automation Botb6971b02020-11-26 17:16:03 -0800317 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800318 ],
319 &quot;name&quot;: &quot;A String&quot;, # The name of the package.
320 },
321 &quot;relatedUrl&quot;: [ # URLs associated with this note
322 { # Metadata for any related URL information
323 &quot;label&quot;: &quot;A String&quot;, # Label to describe usage of the URL
324 &quot;url&quot;: &quot;A String&quot;, # Specific URL to associate with the note
325 },
326 ],
327 &quot;shortDescription&quot;: &quot;A String&quot;, # A one sentence description of this `Note`.
328 &quot;updateTime&quot;: &quot;A String&quot;, # Output only. The time this note was last updated. This field can be used as a filter in list requests.
329 &quot;upgrade&quot;: { # An Upgrade Note represents a potential upgrade of a package to a given version. For each package version combination (i.e. bash 4.0, bash 4.1, bash 4.1.2), there will be a Upgrade Note. # A note describing an upgrade.
330 &quot;distributions&quot;: [ # Metadata about the upgrade for each specific operating system.
331 { # The Upgrade Distribution represents metadata about the Upgrade for each operating system (CPE). Some distributions have additional metadata around updates, classifying them into various categories and severities.
332 &quot;classification&quot;: &quot;A String&quot;, # The operating system classification of this Upgrade, as specified by the upstream operating system upgrade feed.
333 &quot;cpeUri&quot;: &quot;A String&quot;, # Required - The specific operating system this metadata applies to. See https://cpe.mitre.org/specification/.
334 &quot;cve&quot;: [ # The cve that would be resolved by this upgrade.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800335 &quot;A String&quot;,
336 ],
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800337 &quot;severity&quot;: &quot;A String&quot;, # The severity as specified by the upstream operating system.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800338 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800339 ],
340 &quot;package&quot;: &quot;A String&quot;, # Required - The package this Upgrade is for.
341 &quot;version&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # Required - The version of the package in machine + human readable form.
342 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800343 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800344 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
345 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
346 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
347 },
348 },
349 &quot;vulnerabilityType&quot;: { # VulnerabilityType provides metadata about a security vulnerability. # A package vulnerability type of note.
350 &quot;cvssScore&quot;: 3.14, # The CVSS score for this Vulnerability.
351 &quot;details&quot;: [ # All information about the package to specifically identify this vulnerability. One entry per (version range and cpe_uri) the package vulnerability has manifested in.
352 { # Identifies all occurrences of this vulnerability in the package for a specific distro/location For example: glibc in cpe:/o:debian:debian_linux:8 for versions 2.1 - 2.2
353 &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format] (https://cpe.mitre.org/specification/) in which the vulnerability manifests. Examples include distro or storage location for vulnerable jar. This field can be used as a filter in list requests.
354 &quot;description&quot;: &quot;A String&quot;, # A vendor-specific description of this note.
355 &quot;fixedLocation&quot;: { # The location of the vulnerability # The fix for this specific package version.
356 &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format] (https://cpe.mitre.org/specification/) format. Examples include distro or storage location for vulnerable jar. This field can be used as a filter in list requests.
357 &quot;package&quot;: &quot;A String&quot;, # The package being described.
358 &quot;version&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The version of the package being described. This field can be used as a filter in list requests.
359 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800360 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800361 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
362 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
363 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
Yoshi Automation Botb6971b02020-11-26 17:16:03 -0800364 },
Yoshi Automation Bot0d561ef2020-11-25 07:50:41 -0800365 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800366 &quot;isObsolete&quot;: True or False, # Whether this Detail is obsolete. Occurrences are expected not to point to obsolete details.
367 &quot;maxAffectedVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The max version of the package in which the vulnerability exists.
368 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800369 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800370 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
371 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
372 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
373 },
374 &quot;minAffectedVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The min version of the package in which the vulnerability exists.
375 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800376 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800377 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
378 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
379 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
380 },
381 &quot;package&quot;: &quot;A String&quot;, # The name of the package where the vulnerability was found. This field can be used as a filter in list requests.
382 &quot;packageType&quot;: &quot;A String&quot;, # The type of package; whether native or non native(ruby gems, node.js packages etc)
383 &quot;severityName&quot;: &quot;A String&quot;, # The severity (eg: distro assigned severity) for this vulnerability.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800384 &quot;source&quot;: &quot;A String&quot;, # The source from which the information in this Detail was obtained.
Yoshi Automation Bot0d561ef2020-11-25 07:50:41 -0800385 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800386 ],
387 &quot;severity&quot;: &quot;A String&quot;, # Note provider assigned impact of the vulnerability
388 },
389}</pre>
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700390</div>
391
392<div class="method">
393 <code class="details" id="delete">delete(name, x__xgafv=None)</code>
394 <pre>Deletes the given `Note` from the system.
395
396Args:
Dmitry Frenkel3e17f892020-10-06 16:46:05 -0700397 name: string, The name of the note in the form of &quot;providers/{provider_id}/notes/{NOTE_ID}&quot; (required)
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700398 x__xgafv: string, V1 error format.
399 Allowed values
400 1 - v1 error format
401 2 - v2 error format
402
403Returns:
404 An object of the form:
405
Dmitry Frenkel3e17f892020-10-06 16:46:05 -0700406 { # A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); } The JSON representation for `Empty` is empty JSON object `{}`.
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800407}</pre>
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700408</div>
409
410<div class="method">
411 <code class="details" id="get">get(name, x__xgafv=None)</code>
412 <pre>Returns the requested `Note`.
413
414Args:
Dmitry Frenkel3e17f892020-10-06 16:46:05 -0700415 name: string, The name of the note in the form of &quot;providers/{provider_id}/notes/{NOTE_ID}&quot; (required)
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700416 x__xgafv: string, V1 error format.
417 Allowed values
418 1 - v1 error format
419 2 - v2 error format
420
421Returns:
422 An object of the form:
423
424 { # Provides a detailed description of a `Note`.
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800425 &quot;attestationAuthority&quot;: { # Note kind that represents a logical attestation &quot;role&quot; or &quot;authority&quot;. For example, an organization might have one `AttestationAuthority` for &quot;QA&quot; and one for &quot;build&quot;. This Note is intended to act strictly as a grouping mechanism for the attached Occurrences (Attestations). This grouping mechanism also provides a security boundary, since IAM ACLs gate the ability for a principle to attach an Occurrence to a given Note. It also provides a single point of lookup to find all attached Attestation Occurrences, even if they don&#x27;t all live in the same project. # A note describing an attestation role.
426 &quot;hint&quot;: { # This submessage provides human-readable hints about the purpose of the AttestationAuthority. Because the name of a Note acts as its resource reference, it is important to disambiguate the canonical name of the Note (which might be a UUID for security purposes) from &quot;readable&quot; names more suitable for debug output. Note that these hints should NOT be used to look up AttestationAuthorities in security sensitive contexts, such as when looking up Attestations to verify.
427 &quot;humanReadableName&quot;: &quot;A String&quot;, # The human readable name of this Attestation Authority, for example &quot;qa&quot;.
428 },
429 },
430 &quot;baseImage&quot;: { # Basis describes the base image portion (Note) of the DockerImage relationship. Linked occurrences are derived from this or an equivalent image via: FROM Or an equivalent reference, e.g. a tag of the resource_url. # A note describing a base image.
431 &quot;fingerprint&quot;: { # A set of properties that uniquely identify a given Docker image. # The fingerprint of the base image.
432 &quot;v1Name&quot;: &quot;A String&quot;, # The layer-id of the final layer in the Docker image&#x27;s v1 representation. This field can be used as a filter in list requests.
433 &quot;v2Blob&quot;: [ # The ordered list of v2 blobs that represent a given image.
434 &quot;A String&quot;,
435 ],
436 &quot;v2Name&quot;: &quot;A String&quot;, # Output only. The name of the image&#x27;s v2 blobs computed via: [bottom] := v2_blobbottom := sha256(v2_blob[N] + &quot; &quot; + v2_name[N+1]) Only the name of the final blob is kept. This field can be used as a filter in list requests.
437 },
438 &quot;resourceUrl&quot;: &quot;A String&quot;, # The resource_url for the resource representing the basis of associated occurrence images.
439 },
440 &quot;buildType&quot;: { # Note holding the version of the provider&#x27;s builder and the signature of the provenance message in linked BuildDetails. # Build provenance type for a verifiable build.
441 &quot;builderVersion&quot;: &quot;A String&quot;, # Version of the builder which produced this Note.
442 &quot;signature&quot;: { # Message encapsulating the signature of the verified build. # Signature of the build in Occurrences pointing to the Note containing this `BuilderDetails`.
443 &quot;keyId&quot;: &quot;A String&quot;, # An Id for the key used to sign. This could be either an Id for the key stored in `public_key` (such as the Id or fingerprint for a PGP key, or the CN for a cert), or a reference to an external key (such as a reference to a key in Cloud Key Management Service).
444 &quot;keyType&quot;: &quot;A String&quot;, # The type of the key, either stored in `public_key` or referenced in `key_id`
445 &quot;publicKey&quot;: &quot;A String&quot;, # Public key of the builder which can be used to verify that the related findings are valid and unchanged. If `key_type` is empty, this defaults to PEM encoded public keys. This field may be empty if `key_id` references an external key. For Cloud Build based signatures, this is a PEM encoded public key. To verify the Cloud Build signature, place the contents of this field into a file (public.pem). The signature field is base64-decoded into its binary representation in signature.bin, and the provenance bytes from `BuildDetails` are base64-decoded into a binary representation in signed.bin. OpenSSL can then verify the signature: `openssl sha256 -verify public.pem -signature signature.bin signed.bin`
446 &quot;signature&quot;: &quot;A String&quot;, # Signature of the related `BuildProvenance`, encoded in a base64 string.
447 },
448 },
449 &quot;createTime&quot;: &quot;A String&quot;, # Output only. The time this note was created. This field can be used as a filter in list requests.
450 &quot;deployable&quot;: { # An artifact that can be deployed in some runtime. # A note describing something that can be deployed.
451 &quot;resourceUri&quot;: [ # Resource URI for the artifact being deployed.
452 &quot;A String&quot;,
453 ],
454 },
455 &quot;discovery&quot;: { # A note that indicates a type of analysis a provider would perform. This note exists in a provider&#x27;s project. A `Discovery` occurrence is created in a consumer&#x27;s project at the start of analysis. The occurrence&#x27;s operation will indicate the status of the analysis. Absence of an occurrence linked to this note for a resource indicates that analysis hasn&#x27;t started. # A note describing a provider/analysis type.
456 &quot;analysisKind&quot;: &quot;A String&quot;, # The kind of analysis that is handled by this discovery.
457 },
458 &quot;expirationTime&quot;: &quot;A String&quot;, # Time of expiration for this note, null if note does not expire.
459 &quot;kind&quot;: &quot;A String&quot;, # Output only. This explicitly denotes which kind of note is specified. This field can be used as a filter in list requests.
460 &quot;longDescription&quot;: &quot;A String&quot;, # A detailed description of this `Note`.
461 &quot;name&quot;: &quot;A String&quot;, # The name of the note in the form &quot;projects/{provider_project_id}/notes/{NOTE_ID}&quot;
462 &quot;package&quot;: { # This represents a particular package that is distributed over various channels. e.g. glibc (aka libc6) is distributed by many, at various versions. # A note describing a package hosted by various package managers.
463 &quot;distribution&quot;: [ # The various channels by which a package is distributed.
464 { # This represents a particular channel of distribution for a given package. e.g. Debian&#x27;s jessie-backports dpkg mirror
465 &quot;architecture&quot;: &quot;A String&quot;, # The CPU architecture for which packages in this distribution channel were built
466 &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format](https://cpe.mitre.org/specification/) denoting the package manager version distributing a package.
467 &quot;description&quot;: &quot;A String&quot;, # The distribution channel-specific description of this package.
468 &quot;latestVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The latest available version of this package in this distribution channel.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800469 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800470 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800471 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800472 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800473 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
474 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800475 &quot;maintainer&quot;: &quot;A String&quot;, # A freeform string denoting the maintainer of this package.
476 &quot;url&quot;: &quot;A String&quot;, # The distribution channel-specific homepage for this package.
Yoshi Automation Botb6971b02020-11-26 17:16:03 -0800477 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800478 ],
479 &quot;name&quot;: &quot;A String&quot;, # The name of the package.
480 },
481 &quot;relatedUrl&quot;: [ # URLs associated with this note
482 { # Metadata for any related URL information
483 &quot;label&quot;: &quot;A String&quot;, # Label to describe usage of the URL
484 &quot;url&quot;: &quot;A String&quot;, # Specific URL to associate with the note
485 },
486 ],
487 &quot;shortDescription&quot;: &quot;A String&quot;, # A one sentence description of this `Note`.
488 &quot;updateTime&quot;: &quot;A String&quot;, # Output only. The time this note was last updated. This field can be used as a filter in list requests.
489 &quot;upgrade&quot;: { # An Upgrade Note represents a potential upgrade of a package to a given version. For each package version combination (i.e. bash 4.0, bash 4.1, bash 4.1.2), there will be a Upgrade Note. # A note describing an upgrade.
490 &quot;distributions&quot;: [ # Metadata about the upgrade for each specific operating system.
491 { # The Upgrade Distribution represents metadata about the Upgrade for each operating system (CPE). Some distributions have additional metadata around updates, classifying them into various categories and severities.
492 &quot;classification&quot;: &quot;A String&quot;, # The operating system classification of this Upgrade, as specified by the upstream operating system upgrade feed.
493 &quot;cpeUri&quot;: &quot;A String&quot;, # Required - The specific operating system this metadata applies to. See https://cpe.mitre.org/specification/.
494 &quot;cve&quot;: [ # The cve that would be resolved by this upgrade.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800495 &quot;A String&quot;,
496 ],
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800497 &quot;severity&quot;: &quot;A String&quot;, # The severity as specified by the upstream operating system.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800498 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800499 ],
500 &quot;package&quot;: &quot;A String&quot;, # Required - The package this Upgrade is for.
501 &quot;version&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # Required - The version of the package in machine + human readable form.
502 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800503 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800504 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
505 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
506 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
507 },
508 },
509 &quot;vulnerabilityType&quot;: { # VulnerabilityType provides metadata about a security vulnerability. # A package vulnerability type of note.
510 &quot;cvssScore&quot;: 3.14, # The CVSS score for this Vulnerability.
511 &quot;details&quot;: [ # All information about the package to specifically identify this vulnerability. One entry per (version range and cpe_uri) the package vulnerability has manifested in.
512 { # Identifies all occurrences of this vulnerability in the package for a specific distro/location For example: glibc in cpe:/o:debian:debian_linux:8 for versions 2.1 - 2.2
513 &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format] (https://cpe.mitre.org/specification/) in which the vulnerability manifests. Examples include distro or storage location for vulnerable jar. This field can be used as a filter in list requests.
514 &quot;description&quot;: &quot;A String&quot;, # A vendor-specific description of this note.
515 &quot;fixedLocation&quot;: { # The location of the vulnerability # The fix for this specific package version.
516 &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format] (https://cpe.mitre.org/specification/) format. Examples include distro or storage location for vulnerable jar. This field can be used as a filter in list requests.
517 &quot;package&quot;: &quot;A String&quot;, # The package being described.
518 &quot;version&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The version of the package being described. This field can be used as a filter in list requests.
519 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800520 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800521 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
522 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
523 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
Yoshi Automation Botb6971b02020-11-26 17:16:03 -0800524 },
Yoshi Automation Bot0d561ef2020-11-25 07:50:41 -0800525 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800526 &quot;isObsolete&quot;: True or False, # Whether this Detail is obsolete. Occurrences are expected not to point to obsolete details.
527 &quot;maxAffectedVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The max version of the package in which the vulnerability exists.
528 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800529 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800530 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
531 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
532 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
533 },
534 &quot;minAffectedVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The min version of the package in which the vulnerability exists.
535 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800536 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800537 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
538 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
539 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
540 },
541 &quot;package&quot;: &quot;A String&quot;, # The name of the package where the vulnerability was found. This field can be used as a filter in list requests.
542 &quot;packageType&quot;: &quot;A String&quot;, # The type of package; whether native or non native(ruby gems, node.js packages etc)
543 &quot;severityName&quot;: &quot;A String&quot;, # The severity (eg: distro assigned severity) for this vulnerability.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800544 &quot;source&quot;: &quot;A String&quot;, # The source from which the information in this Detail was obtained.
Yoshi Automation Bot0d561ef2020-11-25 07:50:41 -0800545 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800546 ],
547 &quot;severity&quot;: &quot;A String&quot;, # Note provider assigned impact of the vulnerability
548 },
549}</pre>
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700550</div>
551
552<div class="method">
553 <code class="details" id="getIamPolicy">getIamPolicy(resource, body=None, x__xgafv=None)</code>
Dmitry Frenkel3e17f892020-10-06 16:46:05 -0700554 <pre>Gets the access control policy for a note or an `Occurrence` resource. Requires `containeranalysis.notes.setIamPolicy` or `containeranalysis.occurrences.setIamPolicy` permission if the resource is a note or occurrence, respectively. Attempting to call this method on a resource without the required permission will result in a `PERMISSION_DENIED` error. Attempting to call this method on a non-existent resource will result in a `NOT_FOUND` error if the user has list permission on the project, or a `PERMISSION_DENIED` error otherwise. The resource takes the following formats: `projects/{PROJECT_ID}/occurrences/{OCCURRENCE_ID}` for occurrences and projects/{PROJECT_ID}/notes/{NOTE_ID} for notes
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700555
556Args:
Dmitry Frenkel3e17f892020-10-06 16:46:05 -0700557 resource: string, REQUIRED: The resource for which the policy is being requested. See the operation documentation for the appropriate value for this field. (required)
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700558 body: object, The request body.
559 The object takes the form of:
560
561{ # Request message for `GetIamPolicy` method.
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800562 &quot;options&quot;: { # Encapsulates settings provided to GetIamPolicy. # OPTIONAL: A `GetPolicyOptions` object for specifying options to `GetIamPolicy`.
563 &quot;requestedPolicyVersion&quot;: 42, # 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 [IAM documentation](https://cloud.google.com/iam/help/conditions/resource-policies).
564 },
565}
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700566
567 x__xgafv: string, V1 error format.
568 Allowed values
569 1 - v1 error format
570 2 - v2 error format
571
572Returns:
573 An object of the form:
574
Dmitry Frenkel3e17f892020-10-06 16:46:05 -0700575 { # An Identity and Access Management (IAM) policy, which specifies access controls for Google Cloud resources. A `Policy` is a collection of `bindings`. A `binding` binds one or more `members` to a single `role`. Members can be user accounts, service accounts, Google groups, and domains (such as G Suite). A `role` is a named list of permissions; each `role` can be an IAM predefined role or a user-created custom role. For some types of Google Cloud resources, a `binding` can also specify a `condition`, which is a logical expression that allows access to a resource only if the expression evaluates to `true`. A condition can add constraints based on attributes of the request, the resource, or both. To learn which resources support conditions in their IAM policies, see the [IAM documentation](https://cloud.google.com/iam/help/conditions/resource-policies). **JSON example:** { &quot;bindings&quot;: [ { &quot;role&quot;: &quot;roles/resourcemanager.organizationAdmin&quot;, &quot;members&quot;: [ &quot;user:mike@example.com&quot;, &quot;group:admins@example.com&quot;, &quot;domain:google.com&quot;, &quot;serviceAccount:my-project-id@appspot.gserviceaccount.com&quot; ] }, { &quot;role&quot;: &quot;roles/resourcemanager.organizationViewer&quot;, &quot;members&quot;: [ &quot;user:eve@example.com&quot; ], &quot;condition&quot;: { &quot;title&quot;: &quot;expirable access&quot;, &quot;description&quot;: &quot;Does not grant access after Sep 2020&quot;, &quot;expression&quot;: &quot;request.time &lt; timestamp(&#x27;2020-10-01T00:00:00.000Z&#x27;)&quot;, } } ], &quot;etag&quot;: &quot;BwWWja0YfJA=&quot;, &quot;version&quot;: 3 } **YAML example:** bindings: - members: - user:mike@example.com - group:admins@example.com - domain:google.com - serviceAccount:my-project-id@appspot.gserviceaccount.com role: roles/resourcemanager.organizationAdmin - members: - user:eve@example.com role: roles/resourcemanager.organizationViewer condition: title: expirable access description: Does not grant access after Sep 2020 expression: request.time &lt; timestamp(&#x27;2020-10-01T00:00:00.000Z&#x27;) - etag: BwWWja0YfJA= - version: 3 For a description of IAM and its features, see the [IAM documentation](https://cloud.google.com/iam/docs/).
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800576 &quot;bindings&quot;: [ # Associates a list of `members` to a `role`. Optionally, may specify a `condition` that determines how and when the `bindings` are applied. Each of the `bindings` must contain at least one member.
577 { # Associates `members` with a `role`.
578 &quot;condition&quot;: { # Represents a textual expression in the Common Expression Language (CEL) syntax. CEL is a C-like expression language. The syntax and semantics of CEL are documented at https://github.com/google/cel-spec. Example (Comparison): title: &quot;Summary size limit&quot; description: &quot;Determines if a summary is less than 100 chars&quot; expression: &quot;document.summary.size() &lt; 100&quot; Example (Equality): title: &quot;Requestor is owner&quot; description: &quot;Determines if requestor is the document owner&quot; expression: &quot;document.owner == request.auth.claims.email&quot; Example (Logic): title: &quot;Public documents&quot; description: &quot;Determine whether the document should be publicly visible&quot; expression: &quot;document.type != &#x27;private&#x27; &amp;&amp; document.type != &#x27;internal&#x27;&quot; Example (Data Manipulation): title: &quot;Notification string&quot; description: &quot;Create a notification string with a timestamp.&quot; expression: &quot;&#x27;New message received at &#x27; + string(document.create_time)&quot; The exact variables and functions that may be referenced within an expression are determined by the service that evaluates it. See the service documentation for additional information. # The condition that is associated with this binding. If the condition evaluates to `true`, then this binding applies to the current request. If the condition evaluates to `false`, then this binding does not apply to the current request. However, a different role binding might grant the same role to one or more of the members in this binding. To learn which resources support conditions in their IAM policies, see the [IAM documentation](https://cloud.google.com/iam/help/conditions/resource-policies).
579 &quot;description&quot;: &quot;A String&quot;, # Optional. Description of the expression. This is a longer text which describes the expression, e.g. when hovered over it in a UI.
580 &quot;expression&quot;: &quot;A String&quot;, # Textual representation of an expression in Common Expression Language syntax.
581 &quot;location&quot;: &quot;A String&quot;, # Optional. String indicating the location of the expression for error reporting, e.g. a file name and a position in the file.
582 &quot;title&quot;: &quot;A String&quot;, # Optional. Title for the expression, i.e. a short string describing its purpose. This can be used e.g. in UIs which allow to enter the expression.
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700583 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800584 &quot;members&quot;: [ # Specifies the identities requesting access for a Cloud Platform resource. `members` can have the following values: * `allUsers`: A special identifier that represents anyone who is on the internet; with or without a Google account. * `allAuthenticatedUsers`: A special identifier that represents anyone who is authenticated with a Google account or a service account. * `user:{emailid}`: An email address that represents a specific Google account. For example, `alice@example.com` . * `serviceAccount:{emailid}`: An email address that represents a service account. For example, `my-other-app@appspot.gserviceaccount.com`. * `group:{emailid}`: An email address that represents a Google group. For example, `admins@example.com`. * `deleted:user:{emailid}?uid={uniqueid}`: An email address (plus unique identifier) representing a user that has been recently deleted. For example, `alice@example.com?uid=123456789012345678901`. If the user is recovered, this value reverts to `user:{emailid}` and the recovered user retains the role in the binding. * `deleted:serviceAccount:{emailid}?uid={uniqueid}`: An email address (plus unique identifier) representing a service account that has been recently deleted. For example, `my-other-app@appspot.gserviceaccount.com?uid=123456789012345678901`. If the service account is undeleted, this value reverts to `serviceAccount:{emailid}` and the undeleted service account retains the role in the binding. * `deleted:group:{emailid}?uid={uniqueid}`: An email address (plus unique identifier) representing a Google group that has been recently deleted. For example, `admins@example.com?uid=123456789012345678901`. If the group is recovered, this value reverts to `group:{emailid}` and the recovered group retains the role in the binding. * `domain:{domain}`: The G Suite domain (primary) that represents all the users of that domain. For example, `google.com` or `example.com`.
585 &quot;A String&quot;,
586 ],
587 &quot;role&quot;: &quot;A String&quot;, # Role that is assigned to `members`. For example, `roles/viewer`, `roles/editor`, or `roles/owner`.
588 },
589 ],
590 &quot;etag&quot;: &quot;A String&quot;, # `etag` 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 `etag` in the read-modify-write cycle to perform policy updates in order to avoid race conditions: An `etag` is returned in the response to `getIamPolicy`, and systems are expected to put that etag in the request to `setIamPolicy` to ensure that their change will be applied to the same version of the policy. **Important:** If you use IAM Conditions, you must include the `etag` field whenever you call `setIamPolicy`. If you omit this field, then IAM allows you to overwrite a version `3` policy with a version `1` policy, and all of the conditions in the version `3` policy are lost.
591 &quot;version&quot;: 42, # Specifies the format of the policy. Valid values are `0`, `1`, and `3`. Requests that specify an invalid value are rejected. Any operation that affects conditional role bindings must specify version `3`. 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 **Important:** If you use IAM Conditions, you must include the `etag` field whenever you call `setIamPolicy`. If you omit this field, then IAM allows you to overwrite a version `3` policy with a version `1` policy, and all of the conditions in the version `3` 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 [IAM documentation](https://cloud.google.com/iam/help/conditions/resource-policies).
592}</pre>
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700593</div>
594
595<div class="method">
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800596 <code class="details" id="list">list(parent, filter=None, name=None, pageSize=None, pageToken=None, x__xgafv=None)</code>
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700597 <pre>Lists all `Notes` for a given project.
598
599Args:
Bu Sun Kim65020912020-05-20 12:08:20 -0700600 parent: string, This field contains the project Id for example: &quot;projects/{PROJECT_ID}&quot;. (required)
Yoshi Automation Botb6971b02020-11-26 17:16:03 -0800601 filter: string, The filter expression.
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800602 name: string, The name field will contain the project Id for example: &quot;providers/{provider_id} @Deprecated
Yoshi Automation Bot0d561ef2020-11-25 07:50:41 -0800603 pageSize: integer, Number of notes to return in the list.
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800604 pageToken: string, Token to provide to skip to a particular spot in the list.
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700605 x__xgafv: string, V1 error format.
606 Allowed values
607 1 - v1 error format
608 2 - v2 error format
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700609
610Returns:
611 An object of the form:
612
613 { # Response including listed notes.
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800614 &quot;nextPageToken&quot;: &quot;A String&quot;, # The next pagination token in the list response. It should be used as page_token for the following request. An empty value means no more result.
615 &quot;notes&quot;: [ # The occurrences requested
616 { # Provides a detailed description of a `Note`.
617 &quot;attestationAuthority&quot;: { # Note kind that represents a logical attestation &quot;role&quot; or &quot;authority&quot;. For example, an organization might have one `AttestationAuthority` for &quot;QA&quot; and one for &quot;build&quot;. This Note is intended to act strictly as a grouping mechanism for the attached Occurrences (Attestations). This grouping mechanism also provides a security boundary, since IAM ACLs gate the ability for a principle to attach an Occurrence to a given Note. It also provides a single point of lookup to find all attached Attestation Occurrences, even if they don&#x27;t all live in the same project. # A note describing an attestation role.
618 &quot;hint&quot;: { # This submessage provides human-readable hints about the purpose of the AttestationAuthority. Because the name of a Note acts as its resource reference, it is important to disambiguate the canonical name of the Note (which might be a UUID for security purposes) from &quot;readable&quot; names more suitable for debug output. Note that these hints should NOT be used to look up AttestationAuthorities in security sensitive contexts, such as when looking up Attestations to verify.
619 &quot;humanReadableName&quot;: &quot;A String&quot;, # The human readable name of this Attestation Authority, for example &quot;qa&quot;.
620 },
621 },
622 &quot;baseImage&quot;: { # Basis describes the base image portion (Note) of the DockerImage relationship. Linked occurrences are derived from this or an equivalent image via: FROM Or an equivalent reference, e.g. a tag of the resource_url. # A note describing a base image.
623 &quot;fingerprint&quot;: { # A set of properties that uniquely identify a given Docker image. # The fingerprint of the base image.
624 &quot;v1Name&quot;: &quot;A String&quot;, # The layer-id of the final layer in the Docker image&#x27;s v1 representation. This field can be used as a filter in list requests.
625 &quot;v2Blob&quot;: [ # The ordered list of v2 blobs that represent a given image.
626 &quot;A String&quot;,
627 ],
628 &quot;v2Name&quot;: &quot;A String&quot;, # Output only. The name of the image&#x27;s v2 blobs computed via: [bottom] := v2_blobbottom := sha256(v2_blob[N] + &quot; &quot; + v2_name[N+1]) Only the name of the final blob is kept. This field can be used as a filter in list requests.
629 },
630 &quot;resourceUrl&quot;: &quot;A String&quot;, # The resource_url for the resource representing the basis of associated occurrence images.
631 },
632 &quot;buildType&quot;: { # Note holding the version of the provider&#x27;s builder and the signature of the provenance message in linked BuildDetails. # Build provenance type for a verifiable build.
633 &quot;builderVersion&quot;: &quot;A String&quot;, # Version of the builder which produced this Note.
634 &quot;signature&quot;: { # Message encapsulating the signature of the verified build. # Signature of the build in Occurrences pointing to the Note containing this `BuilderDetails`.
635 &quot;keyId&quot;: &quot;A String&quot;, # An Id for the key used to sign. This could be either an Id for the key stored in `public_key` (such as the Id or fingerprint for a PGP key, or the CN for a cert), or a reference to an external key (such as a reference to a key in Cloud Key Management Service).
636 &quot;keyType&quot;: &quot;A String&quot;, # The type of the key, either stored in `public_key` or referenced in `key_id`
637 &quot;publicKey&quot;: &quot;A String&quot;, # Public key of the builder which can be used to verify that the related findings are valid and unchanged. If `key_type` is empty, this defaults to PEM encoded public keys. This field may be empty if `key_id` references an external key. For Cloud Build based signatures, this is a PEM encoded public key. To verify the Cloud Build signature, place the contents of this field into a file (public.pem). The signature field is base64-decoded into its binary representation in signature.bin, and the provenance bytes from `BuildDetails` are base64-decoded into a binary representation in signed.bin. OpenSSL can then verify the signature: `openssl sha256 -verify public.pem -signature signature.bin signed.bin`
638 &quot;signature&quot;: &quot;A String&quot;, # Signature of the related `BuildProvenance`, encoded in a base64 string.
639 },
640 },
641 &quot;createTime&quot;: &quot;A String&quot;, # Output only. The time this note was created. This field can be used as a filter in list requests.
642 &quot;deployable&quot;: { # An artifact that can be deployed in some runtime. # A note describing something that can be deployed.
643 &quot;resourceUri&quot;: [ # Resource URI for the artifact being deployed.
644 &quot;A String&quot;,
645 ],
646 },
647 &quot;discovery&quot;: { # A note that indicates a type of analysis a provider would perform. This note exists in a provider&#x27;s project. A `Discovery` occurrence is created in a consumer&#x27;s project at the start of analysis. The occurrence&#x27;s operation will indicate the status of the analysis. Absence of an occurrence linked to this note for a resource indicates that analysis hasn&#x27;t started. # A note describing a provider/analysis type.
648 &quot;analysisKind&quot;: &quot;A String&quot;, # The kind of analysis that is handled by this discovery.
649 },
650 &quot;expirationTime&quot;: &quot;A String&quot;, # Time of expiration for this note, null if note does not expire.
651 &quot;kind&quot;: &quot;A String&quot;, # Output only. This explicitly denotes which kind of note is specified. This field can be used as a filter in list requests.
652 &quot;longDescription&quot;: &quot;A String&quot;, # A detailed description of this `Note`.
653 &quot;name&quot;: &quot;A String&quot;, # The name of the note in the form &quot;projects/{provider_project_id}/notes/{NOTE_ID}&quot;
654 &quot;package&quot;: { # This represents a particular package that is distributed over various channels. e.g. glibc (aka libc6) is distributed by many, at various versions. # A note describing a package hosted by various package managers.
655 &quot;distribution&quot;: [ # The various channels by which a package is distributed.
656 { # This represents a particular channel of distribution for a given package. e.g. Debian&#x27;s jessie-backports dpkg mirror
657 &quot;architecture&quot;: &quot;A String&quot;, # The CPU architecture for which packages in this distribution channel were built
658 &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format](https://cpe.mitre.org/specification/) denoting the package manager version distributing a package.
659 &quot;description&quot;: &quot;A String&quot;, # The distribution channel-specific description of this package.
660 &quot;latestVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The latest available version of this package in this distribution channel.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800661 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800662 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800663 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800664 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800665 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
666 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800667 &quot;maintainer&quot;: &quot;A String&quot;, # A freeform string denoting the maintainer of this package.
668 &quot;url&quot;: &quot;A String&quot;, # The distribution channel-specific homepage for this package.
Yoshi Automation Botb6971b02020-11-26 17:16:03 -0800669 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800670 ],
671 &quot;name&quot;: &quot;A String&quot;, # The name of the package.
672 },
673 &quot;relatedUrl&quot;: [ # URLs associated with this note
674 { # Metadata for any related URL information
675 &quot;label&quot;: &quot;A String&quot;, # Label to describe usage of the URL
676 &quot;url&quot;: &quot;A String&quot;, # Specific URL to associate with the note
677 },
678 ],
679 &quot;shortDescription&quot;: &quot;A String&quot;, # A one sentence description of this `Note`.
680 &quot;updateTime&quot;: &quot;A String&quot;, # Output only. The time this note was last updated. This field can be used as a filter in list requests.
681 &quot;upgrade&quot;: { # An Upgrade Note represents a potential upgrade of a package to a given version. For each package version combination (i.e. bash 4.0, bash 4.1, bash 4.1.2), there will be a Upgrade Note. # A note describing an upgrade.
682 &quot;distributions&quot;: [ # Metadata about the upgrade for each specific operating system.
683 { # The Upgrade Distribution represents metadata about the Upgrade for each operating system (CPE). Some distributions have additional metadata around updates, classifying them into various categories and severities.
684 &quot;classification&quot;: &quot;A String&quot;, # The operating system classification of this Upgrade, as specified by the upstream operating system upgrade feed.
685 &quot;cpeUri&quot;: &quot;A String&quot;, # Required - The specific operating system this metadata applies to. See https://cpe.mitre.org/specification/.
686 &quot;cve&quot;: [ # The cve that would be resolved by this upgrade.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800687 &quot;A String&quot;,
688 ],
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800689 &quot;severity&quot;: &quot;A String&quot;, # The severity as specified by the upstream operating system.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800690 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800691 ],
692 &quot;package&quot;: &quot;A String&quot;, # Required - The package this Upgrade is for.
693 &quot;version&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # Required - The version of the package in machine + human readable form.
694 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800695 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800696 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
697 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
698 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
Yoshi Automation Bot0d561ef2020-11-25 07:50:41 -0800699 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800700 },
701 &quot;vulnerabilityType&quot;: { # VulnerabilityType provides metadata about a security vulnerability. # A package vulnerability type of note.
702 &quot;cvssScore&quot;: 3.14, # The CVSS score for this Vulnerability.
703 &quot;details&quot;: [ # All information about the package to specifically identify this vulnerability. One entry per (version range and cpe_uri) the package vulnerability has manifested in.
704 { # Identifies all occurrences of this vulnerability in the package for a specific distro/location For example: glibc in cpe:/o:debian:debian_linux:8 for versions 2.1 - 2.2
705 &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format] (https://cpe.mitre.org/specification/) in which the vulnerability manifests. Examples include distro or storage location for vulnerable jar. This field can be used as a filter in list requests.
706 &quot;description&quot;: &quot;A String&quot;, # A vendor-specific description of this note.
707 &quot;fixedLocation&quot;: { # The location of the vulnerability # The fix for this specific package version.
708 &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format] (https://cpe.mitre.org/specification/) format. Examples include distro or storage location for vulnerable jar. This field can be used as a filter in list requests.
709 &quot;package&quot;: &quot;A String&quot;, # The package being described.
710 &quot;version&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The version of the package being described. This field can be used as a filter in list requests.
711 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800712 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800713 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
714 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
715 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
716 },
717 },
718 &quot;isObsolete&quot;: True or False, # Whether this Detail is obsolete. Occurrences are expected not to point to obsolete details.
719 &quot;maxAffectedVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The max version of the package in which the vulnerability exists.
720 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800721 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800722 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
723 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
724 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
725 },
726 &quot;minAffectedVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The min version of the package in which the vulnerability exists.
727 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800728 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800729 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
730 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
731 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
732 },
733 &quot;package&quot;: &quot;A String&quot;, # The name of the package where the vulnerability was found. This field can be used as a filter in list requests.
734 &quot;packageType&quot;: &quot;A String&quot;, # The type of package; whether native or non native(ruby gems, node.js packages etc)
735 &quot;severityName&quot;: &quot;A String&quot;, # The severity (eg: distro assigned severity) for this vulnerability.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800736 &quot;source&quot;: &quot;A String&quot;, # The source from which the information in this Detail was obtained.
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800737 },
738 ],
739 &quot;severity&quot;: &quot;A String&quot;, # Note provider assigned impact of the vulnerability
740 },
741 },
742 ],
743}</pre>
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700744</div>
745
746<div class="method">
747 <code class="details" id="list_next">list_next(previous_request, previous_response)</code>
748 <pre>Retrieves the next page of results.
749
750Args:
751 previous_request: The request for the previous page. (required)
752 previous_response: The response from the request for the previous page. (required)
753
754Returns:
Bu Sun Kim65020912020-05-20 12:08:20 -0700755 A request object that you can call &#x27;execute()&#x27; on to request the next
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700756 page. Returns None if there are no more items in the collection.
757 </pre>
758</div>
759
760<div class="method">
Dan O'Mearadd494642020-05-01 07:42:23 -0700761 <code class="details" id="patch">patch(name, body=None, updateMask=None, x__xgafv=None)</code>
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700762 <pre>Updates an existing `Note`.
763
764Args:
Dmitry Frenkel3e17f892020-10-06 16:46:05 -0700765 name: string, The name of the note. Should be of the form &quot;projects/{provider_id}/notes/{note_id}&quot;. (required)
Dan O'Mearadd494642020-05-01 07:42:23 -0700766 body: object, The request body.
Bu Sun Kim715bd7f2019-06-14 16:50:42 -0700767 The object takes the form of:
768
769{ # Provides a detailed description of a `Note`.
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800770 &quot;attestationAuthority&quot;: { # Note kind that represents a logical attestation &quot;role&quot; or &quot;authority&quot;. For example, an organization might have one `AttestationAuthority` for &quot;QA&quot; and one for &quot;build&quot;. This Note is intended to act strictly as a grouping mechanism for the attached Occurrences (Attestations). This grouping mechanism also provides a security boundary, since IAM ACLs gate the ability for a principle to attach an Occurrence to a given Note. It also provides a single point of lookup to find all attached Attestation Occurrences, even if they don&#x27;t all live in the same project. # A note describing an attestation role.
771 &quot;hint&quot;: { # This submessage provides human-readable hints about the purpose of the AttestationAuthority. Because the name of a Note acts as its resource reference, it is important to disambiguate the canonical name of the Note (which might be a UUID for security purposes) from &quot;readable&quot; names more suitable for debug output. Note that these hints should NOT be used to look up AttestationAuthorities in security sensitive contexts, such as when looking up Attestations to verify.
772 &quot;humanReadableName&quot;: &quot;A String&quot;, # The human readable name of this Attestation Authority, for example &quot;qa&quot;.
Bu Sun Kim673ec5c2020-11-16 11:05:03 -0700773 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800774 },
775 &quot;baseImage&quot;: { # Basis describes the base image portion (Note) of the DockerImage relationship. Linked occurrences are derived from this or an equivalent image via: FROM Or an equivalent reference, e.g. a tag of the resource_url. # A note describing a base image.
776 &quot;fingerprint&quot;: { # A set of properties that uniquely identify a given Docker image. # The fingerprint of the base image.
777 &quot;v1Name&quot;: &quot;A String&quot;, # The layer-id of the final layer in the Docker image&#x27;s v1 representation. This field can be used as a filter in list requests.
778 &quot;v2Blob&quot;: [ # The ordered list of v2 blobs that represent a given image.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800779 &quot;A String&quot;,
780 ],
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800781 &quot;v2Name&quot;: &quot;A String&quot;, # Output only. The name of the image&#x27;s v2 blobs computed via: [bottom] := v2_blobbottom := sha256(v2_blob[N] + &quot; &quot; + v2_name[N+1]) Only the name of the final blob is kept. This field can be used as a filter in list requests.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800782 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800783 &quot;resourceUrl&quot;: &quot;A String&quot;, # The resource_url for the resource representing the basis of associated occurrence images.
784 },
785 &quot;buildType&quot;: { # Note holding the version of the provider&#x27;s builder and the signature of the provenance message in linked BuildDetails. # Build provenance type for a verifiable build.
786 &quot;builderVersion&quot;: &quot;A String&quot;, # Version of the builder which produced this Note.
787 &quot;signature&quot;: { # Message encapsulating the signature of the verified build. # Signature of the build in Occurrences pointing to the Note containing this `BuilderDetails`.
788 &quot;keyId&quot;: &quot;A String&quot;, # An Id for the key used to sign. This could be either an Id for the key stored in `public_key` (such as the Id or fingerprint for a PGP key, or the CN for a cert), or a reference to an external key (such as a reference to a key in Cloud Key Management Service).
789 &quot;keyType&quot;: &quot;A String&quot;, # The type of the key, either stored in `public_key` or referenced in `key_id`
790 &quot;publicKey&quot;: &quot;A String&quot;, # Public key of the builder which can be used to verify that the related findings are valid and unchanged. If `key_type` is empty, this defaults to PEM encoded public keys. This field may be empty if `key_id` references an external key. For Cloud Build based signatures, this is a PEM encoded public key. To verify the Cloud Build signature, place the contents of this field into a file (public.pem). The signature field is base64-decoded into its binary representation in signature.bin, and the provenance bytes from `BuildDetails` are base64-decoded into a binary representation in signed.bin. OpenSSL can then verify the signature: `openssl sha256 -verify public.pem -signature signature.bin signed.bin`
791 &quot;signature&quot;: &quot;A String&quot;, # Signature of the related `BuildProvenance`, encoded in a base64 string.
792 },
793 },
794 &quot;createTime&quot;: &quot;A String&quot;, # Output only. The time this note was created. This field can be used as a filter in list requests.
795 &quot;deployable&quot;: { # An artifact that can be deployed in some runtime. # A note describing something that can be deployed.
796 &quot;resourceUri&quot;: [ # Resource URI for the artifact being deployed.
797 &quot;A String&quot;,
798 ],
799 },
800 &quot;discovery&quot;: { # A note that indicates a type of analysis a provider would perform. This note exists in a provider&#x27;s project. A `Discovery` occurrence is created in a consumer&#x27;s project at the start of analysis. The occurrence&#x27;s operation will indicate the status of the analysis. Absence of an occurrence linked to this note for a resource indicates that analysis hasn&#x27;t started. # A note describing a provider/analysis type.
801 &quot;analysisKind&quot;: &quot;A String&quot;, # The kind of analysis that is handled by this discovery.
802 },
803 &quot;expirationTime&quot;: &quot;A String&quot;, # Time of expiration for this note, null if note does not expire.
804 &quot;kind&quot;: &quot;A String&quot;, # Output only. This explicitly denotes which kind of note is specified. This field can be used as a filter in list requests.
805 &quot;longDescription&quot;: &quot;A String&quot;, # A detailed description of this `Note`.
806 &quot;name&quot;: &quot;A String&quot;, # The name of the note in the form &quot;projects/{provider_project_id}/notes/{NOTE_ID}&quot;
807 &quot;package&quot;: { # This represents a particular package that is distributed over various channels. e.g. glibc (aka libc6) is distributed by many, at various versions. # A note describing a package hosted by various package managers.
808 &quot;distribution&quot;: [ # The various channels by which a package is distributed.
809 { # This represents a particular channel of distribution for a given package. e.g. Debian&#x27;s jessie-backports dpkg mirror
810 &quot;architecture&quot;: &quot;A String&quot;, # The CPU architecture for which packages in this distribution channel were built
811 &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format](https://cpe.mitre.org/specification/) denoting the package manager version distributing a package.
812 &quot;description&quot;: &quot;A String&quot;, # The distribution channel-specific description of this package.
813 &quot;latestVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The latest available version of this package in this distribution channel.
814 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800815 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800816 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
817 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
818 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
819 },
820 &quot;maintainer&quot;: &quot;A String&quot;, # A freeform string denoting the maintainer of this package.
821 &quot;url&quot;: &quot;A String&quot;, # The distribution channel-specific homepage for this package.
822 },
823 ],
824 &quot;name&quot;: &quot;A String&quot;, # The name of the package.
825 },
826 &quot;relatedUrl&quot;: [ # URLs associated with this note
827 { # Metadata for any related URL information
828 &quot;label&quot;: &quot;A String&quot;, # Label to describe usage of the URL
829 &quot;url&quot;: &quot;A String&quot;, # Specific URL to associate with the note
830 },
831 ],
832 &quot;shortDescription&quot;: &quot;A String&quot;, # A one sentence description of this `Note`.
833 &quot;updateTime&quot;: &quot;A String&quot;, # Output only. The time this note was last updated. This field can be used as a filter in list requests.
834 &quot;upgrade&quot;: { # An Upgrade Note represents a potential upgrade of a package to a given version. For each package version combination (i.e. bash 4.0, bash 4.1, bash 4.1.2), there will be a Upgrade Note. # A note describing an upgrade.
835 &quot;distributions&quot;: [ # Metadata about the upgrade for each specific operating system.
836 { # The Upgrade Distribution represents metadata about the Upgrade for each operating system (CPE). Some distributions have additional metadata around updates, classifying them into various categories and severities.
837 &quot;classification&quot;: &quot;A String&quot;, # The operating system classification of this Upgrade, as specified by the upstream operating system upgrade feed.
838 &quot;cpeUri&quot;: &quot;A String&quot;, # Required - The specific operating system this metadata applies to. See https://cpe.mitre.org/specification/.
839 &quot;cve&quot;: [ # The cve that would be resolved by this upgrade.
840 &quot;A String&quot;,
841 ],
842 &quot;severity&quot;: &quot;A String&quot;, # The severity as specified by the upstream operating system.
843 },
844 ],
845 &quot;package&quot;: &quot;A String&quot;, # Required - The package this Upgrade is for.
846 &quot;version&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # Required - The version of the package in machine + human readable form.
847 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800848 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800849 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
850 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
851 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
852 },
853 },
854 &quot;vulnerabilityType&quot;: { # VulnerabilityType provides metadata about a security vulnerability. # A package vulnerability type of note.
855 &quot;cvssScore&quot;: 3.14, # The CVSS score for this Vulnerability.
856 &quot;details&quot;: [ # All information about the package to specifically identify this vulnerability. One entry per (version range and cpe_uri) the package vulnerability has manifested in.
857 { # Identifies all occurrences of this vulnerability in the package for a specific distro/location For example: glibc in cpe:/o:debian:debian_linux:8 for versions 2.1 - 2.2
858 &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format] (https://cpe.mitre.org/specification/) in which the vulnerability manifests. Examples include distro or storage location for vulnerable jar. This field can be used as a filter in list requests.
859 &quot;description&quot;: &quot;A String&quot;, # A vendor-specific description of this note.
860 &quot;fixedLocation&quot;: { # The location of the vulnerability # The fix for this specific package version.
861 &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format] (https://cpe.mitre.org/specification/) format. Examples include distro or storage location for vulnerable jar. This field can be used as a filter in list requests.
862 &quot;package&quot;: &quot;A String&quot;, # The package being described.
863 &quot;version&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The version of the package being described. This field can be used as a filter in list requests.
Yoshi Automation Botb6971b02020-11-26 17:16:03 -0800864 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800865 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botb6971b02020-11-26 17:16:03 -0800866 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800867 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800868 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
869 },
Yoshi Automation Botb6971b02020-11-26 17:16:03 -0800870 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800871 &quot;isObsolete&quot;: True or False, # Whether this Detail is obsolete. Occurrences are expected not to point to obsolete details.
872 &quot;maxAffectedVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The max version of the package in which the vulnerability exists.
873 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800874 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800875 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
876 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
877 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
878 },
879 &quot;minAffectedVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The min version of the package in which the vulnerability exists.
880 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800881 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800882 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
883 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
884 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
885 },
886 &quot;package&quot;: &quot;A String&quot;, # The name of the package where the vulnerability was found. This field can be used as a filter in list requests.
887 &quot;packageType&quot;: &quot;A String&quot;, # The type of package; whether native or non native(ruby gems, node.js packages etc)
888 &quot;severityName&quot;: &quot;A String&quot;, # The severity (eg: distro assigned severity) for this vulnerability.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800889 &quot;source&quot;: &quot;A String&quot;, # The source from which the information in this Detail was obtained.
Yoshi Automation Bot0d561ef2020-11-25 07:50:41 -0800890 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800891 ],
892 &quot;severity&quot;: &quot;A String&quot;, # Note provider assigned impact of the vulnerability
893 },
894}
Bu Sun Kimd059ad82020-07-22 17:02:09 -0700895
896 updateMask: string, The fields to update.
897 x__xgafv: string, V1 error format.
898 Allowed values
899 1 - v1 error format
900 2 - v2 error format
901
902Returns:
903 An object of the form:
904
905 { # Provides a detailed description of a `Note`.
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800906 &quot;attestationAuthority&quot;: { # Note kind that represents a logical attestation &quot;role&quot; or &quot;authority&quot;. For example, an organization might have one `AttestationAuthority` for &quot;QA&quot; and one for &quot;build&quot;. This Note is intended to act strictly as a grouping mechanism for the attached Occurrences (Attestations). This grouping mechanism also provides a security boundary, since IAM ACLs gate the ability for a principle to attach an Occurrence to a given Note. It also provides a single point of lookup to find all attached Attestation Occurrences, even if they don&#x27;t all live in the same project. # A note describing an attestation role.
907 &quot;hint&quot;: { # This submessage provides human-readable hints about the purpose of the AttestationAuthority. Because the name of a Note acts as its resource reference, it is important to disambiguate the canonical name of the Note (which might be a UUID for security purposes) from &quot;readable&quot; names more suitable for debug output. Note that these hints should NOT be used to look up AttestationAuthorities in security sensitive contexts, such as when looking up Attestations to verify.
908 &quot;humanReadableName&quot;: &quot;A String&quot;, # The human readable name of this Attestation Authority, for example &quot;qa&quot;.
909 },
910 },
911 &quot;baseImage&quot;: { # Basis describes the base image portion (Note) of the DockerImage relationship. Linked occurrences are derived from this or an equivalent image via: FROM Or an equivalent reference, e.g. a tag of the resource_url. # A note describing a base image.
912 &quot;fingerprint&quot;: { # A set of properties that uniquely identify a given Docker image. # The fingerprint of the base image.
913 &quot;v1Name&quot;: &quot;A String&quot;, # The layer-id of the final layer in the Docker image&#x27;s v1 representation. This field can be used as a filter in list requests.
914 &quot;v2Blob&quot;: [ # The ordered list of v2 blobs that represent a given image.
915 &quot;A String&quot;,
916 ],
917 &quot;v2Name&quot;: &quot;A String&quot;, # Output only. The name of the image&#x27;s v2 blobs computed via: [bottom] := v2_blobbottom := sha256(v2_blob[N] + &quot; &quot; + v2_name[N+1]) Only the name of the final blob is kept. This field can be used as a filter in list requests.
918 },
919 &quot;resourceUrl&quot;: &quot;A String&quot;, # The resource_url for the resource representing the basis of associated occurrence images.
920 },
921 &quot;buildType&quot;: { # Note holding the version of the provider&#x27;s builder and the signature of the provenance message in linked BuildDetails. # Build provenance type for a verifiable build.
922 &quot;builderVersion&quot;: &quot;A String&quot;, # Version of the builder which produced this Note.
923 &quot;signature&quot;: { # Message encapsulating the signature of the verified build. # Signature of the build in Occurrences pointing to the Note containing this `BuilderDetails`.
924 &quot;keyId&quot;: &quot;A String&quot;, # An Id for the key used to sign. This could be either an Id for the key stored in `public_key` (such as the Id or fingerprint for a PGP key, or the CN for a cert), or a reference to an external key (such as a reference to a key in Cloud Key Management Service).
925 &quot;keyType&quot;: &quot;A String&quot;, # The type of the key, either stored in `public_key` or referenced in `key_id`
926 &quot;publicKey&quot;: &quot;A String&quot;, # Public key of the builder which can be used to verify that the related findings are valid and unchanged. If `key_type` is empty, this defaults to PEM encoded public keys. This field may be empty if `key_id` references an external key. For Cloud Build based signatures, this is a PEM encoded public key. To verify the Cloud Build signature, place the contents of this field into a file (public.pem). The signature field is base64-decoded into its binary representation in signature.bin, and the provenance bytes from `BuildDetails` are base64-decoded into a binary representation in signed.bin. OpenSSL can then verify the signature: `openssl sha256 -verify public.pem -signature signature.bin signed.bin`
927 &quot;signature&quot;: &quot;A String&quot;, # Signature of the related `BuildProvenance`, encoded in a base64 string.
928 },
929 },
930 &quot;createTime&quot;: &quot;A String&quot;, # Output only. The time this note was created. This field can be used as a filter in list requests.
931 &quot;deployable&quot;: { # An artifact that can be deployed in some runtime. # A note describing something that can be deployed.
932 &quot;resourceUri&quot;: [ # Resource URI for the artifact being deployed.
933 &quot;A String&quot;,
934 ],
935 },
936 &quot;discovery&quot;: { # A note that indicates a type of analysis a provider would perform. This note exists in a provider&#x27;s project. A `Discovery` occurrence is created in a consumer&#x27;s project at the start of analysis. The occurrence&#x27;s operation will indicate the status of the analysis. Absence of an occurrence linked to this note for a resource indicates that analysis hasn&#x27;t started. # A note describing a provider/analysis type.
937 &quot;analysisKind&quot;: &quot;A String&quot;, # The kind of analysis that is handled by this discovery.
938 },
939 &quot;expirationTime&quot;: &quot;A String&quot;, # Time of expiration for this note, null if note does not expire.
940 &quot;kind&quot;: &quot;A String&quot;, # Output only. This explicitly denotes which kind of note is specified. This field can be used as a filter in list requests.
941 &quot;longDescription&quot;: &quot;A String&quot;, # A detailed description of this `Note`.
942 &quot;name&quot;: &quot;A String&quot;, # The name of the note in the form &quot;projects/{provider_project_id}/notes/{NOTE_ID}&quot;
943 &quot;package&quot;: { # This represents a particular package that is distributed over various channels. e.g. glibc (aka libc6) is distributed by many, at various versions. # A note describing a package hosted by various package managers.
944 &quot;distribution&quot;: [ # The various channels by which a package is distributed.
945 { # This represents a particular channel of distribution for a given package. e.g. Debian&#x27;s jessie-backports dpkg mirror
946 &quot;architecture&quot;: &quot;A String&quot;, # The CPU architecture for which packages in this distribution channel were built
947 &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format](https://cpe.mitre.org/specification/) denoting the package manager version distributing a package.
948 &quot;description&quot;: &quot;A String&quot;, # The distribution channel-specific description of this package.
949 &quot;latestVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The latest available version of this package in this distribution channel.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800950 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800951 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800952 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800953 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800954 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
955 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800956 &quot;maintainer&quot;: &quot;A String&quot;, # A freeform string denoting the maintainer of this package.
957 &quot;url&quot;: &quot;A String&quot;, # The distribution channel-specific homepage for this package.
Yoshi Automation Botb6971b02020-11-26 17:16:03 -0800958 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800959 ],
960 &quot;name&quot;: &quot;A String&quot;, # The name of the package.
961 },
962 &quot;relatedUrl&quot;: [ # URLs associated with this note
963 { # Metadata for any related URL information
964 &quot;label&quot;: &quot;A String&quot;, # Label to describe usage of the URL
965 &quot;url&quot;: &quot;A String&quot;, # Specific URL to associate with the note
966 },
967 ],
968 &quot;shortDescription&quot;: &quot;A String&quot;, # A one sentence description of this `Note`.
969 &quot;updateTime&quot;: &quot;A String&quot;, # Output only. The time this note was last updated. This field can be used as a filter in list requests.
970 &quot;upgrade&quot;: { # An Upgrade Note represents a potential upgrade of a package to a given version. For each package version combination (i.e. bash 4.0, bash 4.1, bash 4.1.2), there will be a Upgrade Note. # A note describing an upgrade.
971 &quot;distributions&quot;: [ # Metadata about the upgrade for each specific operating system.
972 { # The Upgrade Distribution represents metadata about the Upgrade for each operating system (CPE). Some distributions have additional metadata around updates, classifying them into various categories and severities.
973 &quot;classification&quot;: &quot;A String&quot;, # The operating system classification of this Upgrade, as specified by the upstream operating system upgrade feed.
974 &quot;cpeUri&quot;: &quot;A String&quot;, # Required - The specific operating system this metadata applies to. See https://cpe.mitre.org/specification/.
975 &quot;cve&quot;: [ # The cve that would be resolved by this upgrade.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800976 &quot;A String&quot;,
977 ],
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800978 &quot;severity&quot;: &quot;A String&quot;, # The severity as specified by the upstream operating system.
Yoshi Automation Bot0bf565c2020-12-09 08:56:03 -0800979 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800980 ],
981 &quot;package&quot;: &quot;A String&quot;, # Required - The package this Upgrade is for.
982 &quot;version&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # Required - The version of the package in machine + human readable form.
983 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -0800984 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -0800985 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
986 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
987 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
988 },
989 },
990 &quot;vulnerabilityType&quot;: { # VulnerabilityType provides metadata about a security vulnerability. # A package vulnerability type of note.
991 &quot;cvssScore&quot;: 3.14, # The CVSS score for this Vulnerability.
992 &quot;details&quot;: [ # All information about the package to specifically identify this vulnerability. One entry per (version range and cpe_uri) the package vulnerability has manifested in.
993 { # Identifies all occurrences of this vulnerability in the package for a specific distro/location For example: glibc in cpe:/o:debian:debian_linux:8 for versions 2.1 - 2.2
994 &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format] (https://cpe.mitre.org/specification/) in which the vulnerability manifests. Examples include distro or storage location for vulnerable jar. This field can be used as a filter in list requests.
995 &quot;description&quot;: &quot;A String&quot;, # A vendor-specific description of this note.
996 &quot;fixedLocation&quot;: { # The location of the vulnerability # The fix for this specific package version.
997 &quot;cpeUri&quot;: &quot;A String&quot;, # The cpe_uri in [cpe format] (https://cpe.mitre.org/specification/) format. Examples include distro or storage location for vulnerable jar. This field can be used as a filter in list requests.
998 &quot;package&quot;: &quot;A String&quot;, # The package being described.
999 &quot;version&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The version of the package being described. This field can be used as a filter in list requests.
1000 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -08001001 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -08001002 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
1003 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
1004 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
Yoshi Automation Botb6971b02020-11-26 17:16:03 -08001005 },
Yoshi Automation Bot0d561ef2020-11-25 07:50:41 -08001006 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -08001007 &quot;isObsolete&quot;: True or False, # Whether this Detail is obsolete. Occurrences are expected not to point to obsolete details.
1008 &quot;maxAffectedVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The max version of the package in which the vulnerability exists.
1009 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -08001010 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -08001011 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
1012 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
1013 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
1014 },
1015 &quot;minAffectedVersion&quot;: { # Version contains structured information about the version of the package. For a discussion of this in Debian/Ubuntu: http://serverfault.com/questions/604541/debian-packages-version-convention For a discussion of this in Redhat/Fedora/Centos: http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/ # The min version of the package in which the vulnerability exists.
1016 &quot;epoch&quot;: 42, # Used to correct mistakes in the version numbering scheme.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -08001017 &quot;inclusive&quot;: True or False, # Whether this version is vulnerable, when defining the version bounds. For example, if the minimum version is 2.0, inclusive=true would say 2.0 is vulnerable, while inclusive=false would say it&#x27;s not
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -08001018 &quot;kind&quot;: &quot;A String&quot;, # Distinguish between sentinel MIN/MAX versions and normal versions. If kind is not NORMAL, then the other fields are ignored.
1019 &quot;name&quot;: &quot;A String&quot;, # The main part of the version name.
1020 &quot;revision&quot;: &quot;A String&quot;, # The iteration of the package build from the above version.
1021 },
1022 &quot;package&quot;: &quot;A String&quot;, # The name of the package where the vulnerability was found. This field can be used as a filter in list requests.
1023 &quot;packageType&quot;: &quot;A String&quot;, # The type of package; whether native or non native(ruby gems, node.js packages etc)
1024 &quot;severityName&quot;: &quot;A String&quot;, # The severity (eg: distro assigned severity) for this vulnerability.
yoshi-code-botb6dc1b92021-03-02 11:49:08 -08001025 &quot;source&quot;: &quot;A String&quot;, # The source from which the information in this Detail was obtained.
Yoshi Automation Bot0d561ef2020-11-25 07:50:41 -08001026 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -08001027 ],
1028 &quot;severity&quot;: &quot;A String&quot;, # Note provider assigned impact of the vulnerability
1029 },
1030}</pre>
Bu Sun Kim715bd7f2019-06-14 16:50:42 -07001031</div>
1032
1033<div class="method">
Dan O'Mearadd494642020-05-01 07:42:23 -07001034 <code class="details" id="setIamPolicy">setIamPolicy(resource, body=None, x__xgafv=None)</code>
Dmitry Frenkel3e17f892020-10-06 16:46:05 -07001035 <pre>Sets the access control policy on the specified `Note` or `Occurrence`. Requires `containeranalysis.notes.setIamPolicy` or `containeranalysis.occurrences.setIamPolicy` permission if the resource is a `Note` or an `Occurrence`, respectively. Attempting to call this method without these permissions will result in a ` `PERMISSION_DENIED` error. Attempting to call this method on a non-existent resource will result in a `NOT_FOUND` error if the user has `containeranalysis.notes.list` permission on a `Note` or `containeranalysis.occurrences.list` on an `Occurrence`, or a `PERMISSION_DENIED` error otherwise. The resource takes the following formats: `projects/{projectid}/occurrences/{occurrenceid}` for occurrences and projects/{projectid}/notes/{noteid} for notes
Bu Sun Kim715bd7f2019-06-14 16:50:42 -07001036
1037Args:
Dmitry Frenkel3e17f892020-10-06 16:46:05 -07001038 resource: string, REQUIRED: The resource for which the policy is being specified. See the operation documentation for the appropriate value for this field. (required)
Dan O'Mearadd494642020-05-01 07:42:23 -07001039 body: object, The request body.
Bu Sun Kim715bd7f2019-06-14 16:50:42 -07001040 The object takes the form of:
1041
1042{ # Request message for `SetIamPolicy` method.
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -08001043 &quot;policy&quot;: { # An Identity and Access Management (IAM) policy, which specifies access controls for Google Cloud resources. A `Policy` is a collection of `bindings`. A `binding` binds one or more `members` to a single `role`. Members can be user accounts, service accounts, Google groups, and domains (such as G Suite). A `role` is a named list of permissions; each `role` can be an IAM predefined role or a user-created custom role. For some types of Google Cloud resources, a `binding` can also specify a `condition`, which is a logical expression that allows access to a resource only if the expression evaluates to `true`. A condition can add constraints based on attributes of the request, the resource, or both. To learn which resources support conditions in their IAM policies, see the [IAM documentation](https://cloud.google.com/iam/help/conditions/resource-policies). **JSON example:** { &quot;bindings&quot;: [ { &quot;role&quot;: &quot;roles/resourcemanager.organizationAdmin&quot;, &quot;members&quot;: [ &quot;user:mike@example.com&quot;, &quot;group:admins@example.com&quot;, &quot;domain:google.com&quot;, &quot;serviceAccount:my-project-id@appspot.gserviceaccount.com&quot; ] }, { &quot;role&quot;: &quot;roles/resourcemanager.organizationViewer&quot;, &quot;members&quot;: [ &quot;user:eve@example.com&quot; ], &quot;condition&quot;: { &quot;title&quot;: &quot;expirable access&quot;, &quot;description&quot;: &quot;Does not grant access after Sep 2020&quot;, &quot;expression&quot;: &quot;request.time &lt; timestamp(&#x27;2020-10-01T00:00:00.000Z&#x27;)&quot;, } } ], &quot;etag&quot;: &quot;BwWWja0YfJA=&quot;, &quot;version&quot;: 3 } **YAML example:** bindings: - members: - user:mike@example.com - group:admins@example.com - domain:google.com - serviceAccount:my-project-id@appspot.gserviceaccount.com role: roles/resourcemanager.organizationAdmin - members: - user:eve@example.com role: roles/resourcemanager.organizationViewer condition: title: expirable access description: Does not grant access after Sep 2020 expression: request.time &lt; timestamp(&#x27;2020-10-01T00:00:00.000Z&#x27;) - etag: BwWWja0YfJA= - version: 3 For a description of IAM and its features, see the [IAM documentation](https://cloud.google.com/iam/docs/). # REQUIRED: The complete policy to be applied to the `resource`. The size of the policy is limited to a few 10s of KB. An empty policy is a valid policy but certain Cloud Platform services (such as Projects) might reject them.
1044 &quot;bindings&quot;: [ # Associates a list of `members` to a `role`. Optionally, may specify a `condition` that determines how and when the `bindings` are applied. Each of the `bindings` must contain at least one member.
1045 { # Associates `members` with a `role`.
1046 &quot;condition&quot;: { # Represents a textual expression in the Common Expression Language (CEL) syntax. CEL is a C-like expression language. The syntax and semantics of CEL are documented at https://github.com/google/cel-spec. Example (Comparison): title: &quot;Summary size limit&quot; description: &quot;Determines if a summary is less than 100 chars&quot; expression: &quot;document.summary.size() &lt; 100&quot; Example (Equality): title: &quot;Requestor is owner&quot; description: &quot;Determines if requestor is the document owner&quot; expression: &quot;document.owner == request.auth.claims.email&quot; Example (Logic): title: &quot;Public documents&quot; description: &quot;Determine whether the document should be publicly visible&quot; expression: &quot;document.type != &#x27;private&#x27; &amp;&amp; document.type != &#x27;internal&#x27;&quot; Example (Data Manipulation): title: &quot;Notification string&quot; description: &quot;Create a notification string with a timestamp.&quot; expression: &quot;&#x27;New message received at &#x27; + string(document.create_time)&quot; The exact variables and functions that may be referenced within an expression are determined by the service that evaluates it. See the service documentation for additional information. # The condition that is associated with this binding. If the condition evaluates to `true`, then this binding applies to the current request. If the condition evaluates to `false`, then this binding does not apply to the current request. However, a different role binding might grant the same role to one or more of the members in this binding. To learn which resources support conditions in their IAM policies, see the [IAM documentation](https://cloud.google.com/iam/help/conditions/resource-policies).
1047 &quot;description&quot;: &quot;A String&quot;, # Optional. Description of the expression. This is a longer text which describes the expression, e.g. when hovered over it in a UI.
1048 &quot;expression&quot;: &quot;A String&quot;, # Textual representation of an expression in Common Expression Language syntax.
1049 &quot;location&quot;: &quot;A String&quot;, # Optional. String indicating the location of the expression for error reporting, e.g. a file name and a position in the file.
1050 &quot;title&quot;: &quot;A String&quot;, # Optional. Title for the expression, i.e. a short string describing its purpose. This can be used e.g. in UIs which allow to enter the expression.
Bu Sun Kim715bd7f2019-06-14 16:50:42 -07001051 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -08001052 &quot;members&quot;: [ # Specifies the identities requesting access for a Cloud Platform resource. `members` can have the following values: * `allUsers`: A special identifier that represents anyone who is on the internet; with or without a Google account. * `allAuthenticatedUsers`: A special identifier that represents anyone who is authenticated with a Google account or a service account. * `user:{emailid}`: An email address that represents a specific Google account. For example, `alice@example.com` . * `serviceAccount:{emailid}`: An email address that represents a service account. For example, `my-other-app@appspot.gserviceaccount.com`. * `group:{emailid}`: An email address that represents a Google group. For example, `admins@example.com`. * `deleted:user:{emailid}?uid={uniqueid}`: An email address (plus unique identifier) representing a user that has been recently deleted. For example, `alice@example.com?uid=123456789012345678901`. If the user is recovered, this value reverts to `user:{emailid}` and the recovered user retains the role in the binding. * `deleted:serviceAccount:{emailid}?uid={uniqueid}`: An email address (plus unique identifier) representing a service account that has been recently deleted. For example, `my-other-app@appspot.gserviceaccount.com?uid=123456789012345678901`. If the service account is undeleted, this value reverts to `serviceAccount:{emailid}` and the undeleted service account retains the role in the binding. * `deleted:group:{emailid}?uid={uniqueid}`: An email address (plus unique identifier) representing a Google group that has been recently deleted. For example, `admins@example.com?uid=123456789012345678901`. If the group is recovered, this value reverts to `group:{emailid}` and the recovered group retains the role in the binding. * `domain:{domain}`: The G Suite domain (primary) that represents all the users of that domain. For example, `google.com` or `example.com`.
1053 &quot;A String&quot;,
1054 ],
1055 &quot;role&quot;: &quot;A String&quot;, # Role that is assigned to `members`. For example, `roles/viewer`, `roles/editor`, or `roles/owner`.
1056 },
1057 ],
1058 &quot;etag&quot;: &quot;A String&quot;, # `etag` 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 `etag` in the read-modify-write cycle to perform policy updates in order to avoid race conditions: An `etag` is returned in the response to `getIamPolicy`, and systems are expected to put that etag in the request to `setIamPolicy` to ensure that their change will be applied to the same version of the policy. **Important:** If you use IAM Conditions, you must include the `etag` field whenever you call `setIamPolicy`. If you omit this field, then IAM allows you to overwrite a version `3` policy with a version `1` policy, and all of the conditions in the version `3` policy are lost.
1059 &quot;version&quot;: 42, # Specifies the format of the policy. Valid values are `0`, `1`, and `3`. Requests that specify an invalid value are rejected. Any operation that affects conditional role bindings must specify version `3`. 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 **Important:** If you use IAM Conditions, you must include the `etag` field whenever you call `setIamPolicy`. If you omit this field, then IAM allows you to overwrite a version `3` policy with a version `1` policy, and all of the conditions in the version `3` 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 [IAM documentation](https://cloud.google.com/iam/help/conditions/resource-policies).
1060 },
1061}
Bu Sun Kim715bd7f2019-06-14 16:50:42 -07001062
1063 x__xgafv: string, V1 error format.
1064 Allowed values
1065 1 - v1 error format
1066 2 - v2 error format
1067
1068Returns:
1069 An object of the form:
1070
Dmitry Frenkel3e17f892020-10-06 16:46:05 -07001071 { # An Identity and Access Management (IAM) policy, which specifies access controls for Google Cloud resources. A `Policy` is a collection of `bindings`. A `binding` binds one or more `members` to a single `role`. Members can be user accounts, service accounts, Google groups, and domains (such as G Suite). A `role` is a named list of permissions; each `role` can be an IAM predefined role or a user-created custom role. For some types of Google Cloud resources, a `binding` can also specify a `condition`, which is a logical expression that allows access to a resource only if the expression evaluates to `true`. A condition can add constraints based on attributes of the request, the resource, or both. To learn which resources support conditions in their IAM policies, see the [IAM documentation](https://cloud.google.com/iam/help/conditions/resource-policies). **JSON example:** { &quot;bindings&quot;: [ { &quot;role&quot;: &quot;roles/resourcemanager.organizationAdmin&quot;, &quot;members&quot;: [ &quot;user:mike@example.com&quot;, &quot;group:admins@example.com&quot;, &quot;domain:google.com&quot;, &quot;serviceAccount:my-project-id@appspot.gserviceaccount.com&quot; ] }, { &quot;role&quot;: &quot;roles/resourcemanager.organizationViewer&quot;, &quot;members&quot;: [ &quot;user:eve@example.com&quot; ], &quot;condition&quot;: { &quot;title&quot;: &quot;expirable access&quot;, &quot;description&quot;: &quot;Does not grant access after Sep 2020&quot;, &quot;expression&quot;: &quot;request.time &lt; timestamp(&#x27;2020-10-01T00:00:00.000Z&#x27;)&quot;, } } ], &quot;etag&quot;: &quot;BwWWja0YfJA=&quot;, &quot;version&quot;: 3 } **YAML example:** bindings: - members: - user:mike@example.com - group:admins@example.com - domain:google.com - serviceAccount:my-project-id@appspot.gserviceaccount.com role: roles/resourcemanager.organizationAdmin - members: - user:eve@example.com role: roles/resourcemanager.organizationViewer condition: title: expirable access description: Does not grant access after Sep 2020 expression: request.time &lt; timestamp(&#x27;2020-10-01T00:00:00.000Z&#x27;) - etag: BwWWja0YfJA= - version: 3 For a description of IAM and its features, see the [IAM documentation](https://cloud.google.com/iam/docs/).
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -08001072 &quot;bindings&quot;: [ # Associates a list of `members` to a `role`. Optionally, may specify a `condition` that determines how and when the `bindings` are applied. Each of the `bindings` must contain at least one member.
1073 { # Associates `members` with a `role`.
1074 &quot;condition&quot;: { # Represents a textual expression in the Common Expression Language (CEL) syntax. CEL is a C-like expression language. The syntax and semantics of CEL are documented at https://github.com/google/cel-spec. Example (Comparison): title: &quot;Summary size limit&quot; description: &quot;Determines if a summary is less than 100 chars&quot; expression: &quot;document.summary.size() &lt; 100&quot; Example (Equality): title: &quot;Requestor is owner&quot; description: &quot;Determines if requestor is the document owner&quot; expression: &quot;document.owner == request.auth.claims.email&quot; Example (Logic): title: &quot;Public documents&quot; description: &quot;Determine whether the document should be publicly visible&quot; expression: &quot;document.type != &#x27;private&#x27; &amp;&amp; document.type != &#x27;internal&#x27;&quot; Example (Data Manipulation): title: &quot;Notification string&quot; description: &quot;Create a notification string with a timestamp.&quot; expression: &quot;&#x27;New message received at &#x27; + string(document.create_time)&quot; The exact variables and functions that may be referenced within an expression are determined by the service that evaluates it. See the service documentation for additional information. # The condition that is associated with this binding. If the condition evaluates to `true`, then this binding applies to the current request. If the condition evaluates to `false`, then this binding does not apply to the current request. However, a different role binding might grant the same role to one or more of the members in this binding. To learn which resources support conditions in their IAM policies, see the [IAM documentation](https://cloud.google.com/iam/help/conditions/resource-policies).
1075 &quot;description&quot;: &quot;A String&quot;, # Optional. Description of the expression. This is a longer text which describes the expression, e.g. when hovered over it in a UI.
1076 &quot;expression&quot;: &quot;A String&quot;, # Textual representation of an expression in Common Expression Language syntax.
1077 &quot;location&quot;: &quot;A String&quot;, # Optional. String indicating the location of the expression for error reporting, e.g. a file name and a position in the file.
1078 &quot;title&quot;: &quot;A String&quot;, # Optional. Title for the expression, i.e. a short string describing its purpose. This can be used e.g. in UIs which allow to enter the expression.
Bu Sun Kim715bd7f2019-06-14 16:50:42 -07001079 },
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -08001080 &quot;members&quot;: [ # Specifies the identities requesting access for a Cloud Platform resource. `members` can have the following values: * `allUsers`: A special identifier that represents anyone who is on the internet; with or without a Google account. * `allAuthenticatedUsers`: A special identifier that represents anyone who is authenticated with a Google account or a service account. * `user:{emailid}`: An email address that represents a specific Google account. For example, `alice@example.com` . * `serviceAccount:{emailid}`: An email address that represents a service account. For example, `my-other-app@appspot.gserviceaccount.com`. * `group:{emailid}`: An email address that represents a Google group. For example, `admins@example.com`. * `deleted:user:{emailid}?uid={uniqueid}`: An email address (plus unique identifier) representing a user that has been recently deleted. For example, `alice@example.com?uid=123456789012345678901`. If the user is recovered, this value reverts to `user:{emailid}` and the recovered user retains the role in the binding. * `deleted:serviceAccount:{emailid}?uid={uniqueid}`: An email address (plus unique identifier) representing a service account that has been recently deleted. For example, `my-other-app@appspot.gserviceaccount.com?uid=123456789012345678901`. If the service account is undeleted, this value reverts to `serviceAccount:{emailid}` and the undeleted service account retains the role in the binding. * `deleted:group:{emailid}?uid={uniqueid}`: An email address (plus unique identifier) representing a Google group that has been recently deleted. For example, `admins@example.com?uid=123456789012345678901`. If the group is recovered, this value reverts to `group:{emailid}` and the recovered group retains the role in the binding. * `domain:{domain}`: The G Suite domain (primary) that represents all the users of that domain. For example, `google.com` or `example.com`.
1081 &quot;A String&quot;,
1082 ],
1083 &quot;role&quot;: &quot;A String&quot;, # Role that is assigned to `members`. For example, `roles/viewer`, `roles/editor`, or `roles/owner`.
1084 },
1085 ],
1086 &quot;etag&quot;: &quot;A String&quot;, # `etag` 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 `etag` in the read-modify-write cycle to perform policy updates in order to avoid race conditions: An `etag` is returned in the response to `getIamPolicy`, and systems are expected to put that etag in the request to `setIamPolicy` to ensure that their change will be applied to the same version of the policy. **Important:** If you use IAM Conditions, you must include the `etag` field whenever you call `setIamPolicy`. If you omit this field, then IAM allows you to overwrite a version `3` policy with a version `1` policy, and all of the conditions in the version `3` policy are lost.
1087 &quot;version&quot;: 42, # Specifies the format of the policy. Valid values are `0`, `1`, and `3`. Requests that specify an invalid value are rejected. Any operation that affects conditional role bindings must specify version `3`. 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 **Important:** If you use IAM Conditions, you must include the `etag` field whenever you call `setIamPolicy`. If you omit this field, then IAM allows you to overwrite a version `3` policy with a version `1` policy, and all of the conditions in the version `3` 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 [IAM documentation](https://cloud.google.com/iam/help/conditions/resource-policies).
1088}</pre>
Bu Sun Kim715bd7f2019-06-14 16:50:42 -07001089</div>
1090
1091<div class="method">
Dan O'Mearadd494642020-05-01 07:42:23 -07001092 <code class="details" id="testIamPermissions">testIamPermissions(resource, body=None, x__xgafv=None)</code>
Dmitry Frenkel3e17f892020-10-06 16:46:05 -07001093 <pre>Returns the permissions that a caller has on the specified note or occurrence resource. Requires list permission on the project (for example, &quot;storage.objects.list&quot; on the containing bucket for testing permission of an object). Attempting to call this method on a non-existent resource will result in a `NOT_FOUND` error if the user has list permission on the project, or a `PERMISSION_DENIED` error otherwise. The resource takes the following formats: `projects/{PROJECT_ID}/occurrences/{OCCURRENCE_ID}` for `Occurrences` and `projects/{PROJECT_ID}/notes/{NOTE_ID}` for `Notes`
Bu Sun Kim715bd7f2019-06-14 16:50:42 -07001094
1095Args:
Dmitry Frenkel3e17f892020-10-06 16:46:05 -07001096 resource: string, REQUIRED: The resource for which the policy detail is being requested. See the operation documentation for the appropriate value for this field. (required)
Dan O'Mearadd494642020-05-01 07:42:23 -07001097 body: object, The request body.
Bu Sun Kim715bd7f2019-06-14 16:50:42 -07001098 The object takes the form of:
1099
1100{ # Request message for `TestIamPermissions` method.
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -08001101 &quot;permissions&quot;: [ # The set of permissions to check for the `resource`. Permissions with wildcards (such as &#x27;*&#x27; or &#x27;storage.*&#x27;) are not allowed. For more information see [IAM Overview](https://cloud.google.com/iam/docs/overview#permissions).
1102 &quot;A String&quot;,
1103 ],
1104}
Bu Sun Kim715bd7f2019-06-14 16:50:42 -07001105
1106 x__xgafv: string, V1 error format.
1107 Allowed values
1108 1 - v1 error format
1109 2 - v2 error format
1110
1111Returns:
1112 An object of the form:
1113
1114 { # Response message for `TestIamPermissions` method.
Yoshi Automation Botcc94ec82021-01-15 07:10:04 -08001115 &quot;permissions&quot;: [ # A subset of `TestPermissionsRequest.permissions` that the caller is allowed.
1116 &quot;A String&quot;,
1117 ],
1118}</pre>
Bu Sun Kim715bd7f2019-06-14 16:50:42 -07001119</div>
1120
1121</body></html>