You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#### containeranalysis:v1
The following keys were added:
- schemas.Note.properties.advisoryPublishTime (Total Keys: 2)
#### containeranalysis:v1beta1
The following keys were added:
- schemas.Note.properties.advisoryPublishTime (Total Keys: 2)
Copy file name to clipboardExpand all lines: docs/dyn/containeranalysis_v1.projects.locations.notes.html
+8Lines changed: 8 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -125,6 +125,7 @@ <h3>Method Details</h3>
125
125
{ # Request to create notes in batch.
126
126
"notes": { # Required. The notes to create. Max allowed length is 1000.
127
127
"a_key": { # A type of analysis that can be done for a resource.
128
+
"advisoryPublishTime": "A String", # The timestamp when the advisory was first published by the source feed.
128
129
"attestation": { # Note kind that represents a logical attestation "role" or "authority". For example, an organization might have one `Authority` for "QA" and one for "build". 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't all live in the same project. # A note describing an attestation role.
129
130
"hint": { # This submessage provides human-readable hints about the purpose of the authority. 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 "readable" names more suitable for debug output. Note that these hints should not be used to look up authorities in security sensitive contexts, such as when looking up attestations to verify. # Hint hints at the purpose of the attestation authority.
130
131
"humanReadableName": "A String", # Required. The human readable name of this attestation authority, for example "qa".
@@ -427,6 +428,7 @@ <h3>Method Details</h3>
427
428
{ # Response for creating notes in batch.
428
429
"notes": [ # The notes that were created.
429
430
{ # A type of analysis that can be done for a resource.
431
+
"advisoryPublishTime": "A String", # The timestamp when the advisory was first published by the source feed.
430
432
"attestation": { # Note kind that represents a logical attestation "role" or "authority". For example, an organization might have one `Authority` for "QA" and one for "build". 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't all live in the same project. # A note describing an attestation role.
431
433
"hint": { # This submessage provides human-readable hints about the purpose of the authority. 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 "readable" names more suitable for debug output. Note that these hints should not be used to look up authorities in security sensitive contexts, such as when looking up attestations to verify. # Hint hints at the purpose of the attestation authority.
432
434
"humanReadableName": "A String", # Required. The human readable name of this attestation authority, for example "qa".
@@ -734,6 +736,7 @@ <h3>Method Details</h3>
734
736
The object takes the form of:
735
737
736
738
{ # A type of analysis that can be done for a resource.
739
+
"advisoryPublishTime": "A String", # The timestamp when the advisory was first published by the source feed.
737
740
"attestation": { # Note kind that represents a logical attestation "role" or "authority". For example, an organization might have one `Authority` for "QA" and one for "build". 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't all live in the same project. # A note describing an attestation role.
738
741
"hint": { # This submessage provides human-readable hints about the purpose of the authority. 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 "readable" names more suitable for debug output. Note that these hints should not be used to look up authorities in security sensitive contexts, such as when looking up attestations to verify. # Hint hints at the purpose of the attestation authority.
739
742
"humanReadableName": "A String", # Required. The human readable name of this attestation authority, for example "qa".
@@ -1033,6 +1036,7 @@ <h3>Method Details</h3>
1033
1036
An object of the form:
1034
1037
1035
1038
{ # A type of analysis that can be done for a resource.
1039
+
"advisoryPublishTime": "A String", # The timestamp when the advisory was first published by the source feed.
1036
1040
"attestation": { # Note kind that represents a logical attestation "role" or "authority". For example, an organization might have one `Authority` for "QA" and one for "build". 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't all live in the same project. # A note describing an attestation role.
1037
1041
"hint": { # This submessage provides human-readable hints about the purpose of the authority. 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 "readable" names more suitable for debug output. Note that these hints should not be used to look up authorities in security sensitive contexts, such as when looking up attestations to verify. # Hint hints at the purpose of the attestation authority.
1038
1042
"humanReadableName": "A String", # Required. The human readable name of this attestation authority, for example "qa".
@@ -1356,6 +1360,7 @@ <h3>Method Details</h3>
1356
1360
An object of the form:
1357
1361
1358
1362
{ # A type of analysis that can be done for a resource.
1363
+
"advisoryPublishTime": "A String", # The timestamp when the advisory was first published by the source feed.
1359
1364
"attestation": { # Note kind that represents a logical attestation "role" or "authority". For example, an organization might have one `Authority` for "QA" and one for "build". 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't all live in the same project. # A note describing an attestation role.
1360
1365
"hint": { # This submessage provides human-readable hints about the purpose of the authority. 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 "readable" names more suitable for debug output. Note that these hints should not be used to look up authorities in security sensitive contexts, such as when looking up attestations to verify. # Hint hints at the purpose of the attestation authority.
1361
1366
"humanReadableName": "A String", # Required. The human readable name of this attestation authority, for example "qa".
@@ -1711,6 +1716,7 @@ <h3>Method Details</h3>
1711
1716
"nextPageToken": "A String", # 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 results.
1712
1717
"notes": [ # The notes requested.
1713
1718
{ # A type of analysis that can be done for a resource.
1719
+
"advisoryPublishTime": "A String", # The timestamp when the advisory was first published by the source feed.
1714
1720
"attestation": { # Note kind that represents a logical attestation "role" or "authority". For example, an organization might have one `Authority` for "QA" and one for "build". 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't all live in the same project. # A note describing an attestation role.
1715
1721
"hint": { # This submessage provides human-readable hints about the purpose of the authority. 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 "readable" names more suitable for debug output. Note that these hints should not be used to look up authorities in security sensitive contexts, such as when looking up attestations to verify. # Hint hints at the purpose of the attestation authority.
1716
1722
"humanReadableName": "A String", # Required. The human readable name of this attestation authority, for example "qa".
@@ -2030,6 +2036,7 @@ <h3>Method Details</h3>
2030
2036
The object takes the form of:
2031
2037
2032
2038
{ # A type of analysis that can be done for a resource.
2039
+
"advisoryPublishTime": "A String", # The timestamp when the advisory was first published by the source feed.
2033
2040
"attestation": { # Note kind that represents a logical attestation "role" or "authority". For example, an organization might have one `Authority` for "QA" and one for "build". 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't all live in the same project. # A note describing an attestation role.
2034
2041
"hint": { # This submessage provides human-readable hints about the purpose of the authority. 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 "readable" names more suitable for debug output. Note that these hints should not be used to look up authorities in security sensitive contexts, such as when looking up attestations to verify. # Hint hints at the purpose of the attestation authority.
2035
2042
"humanReadableName": "A String", # Required. The human readable name of this attestation authority, for example "qa".
@@ -2329,6 +2336,7 @@ <h3>Method Details</h3>
2329
2336
An object of the form:
2330
2337
2331
2338
{ # A type of analysis that can be done for a resource.
2339
+
"advisoryPublishTime": "A String", # The timestamp when the advisory was first published by the source feed.
2332
2340
"attestation": { # Note kind that represents a logical attestation "role" or "authority". For example, an organization might have one `Authority` for "QA" and one for "build". 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't all live in the same project. # A note describing an attestation role.
2333
2341
"hint": { # This submessage provides human-readable hints about the purpose of the authority. 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 "readable" names more suitable for debug output. Note that these hints should not be used to look up authorities in security sensitive contexts, such as when looking up attestations to verify. # Hint hints at the purpose of the attestation authority.
2334
2342
"humanReadableName": "A String", # Required. The human readable name of this attestation authority, for example "qa".
Copy file name to clipboardExpand all lines: docs/dyn/containeranalysis_v1.projects.locations.occurrences.html
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -4629,6 +4629,7 @@ <h3>Method Details</h3>
4629
4629
An object of the form:
4630
4630
4631
4631
{ # A type of analysis that can be done for a resource.
4632
+
"advisoryPublishTime": "A String", # The timestamp when the advisory was first published by the source feed.
4632
4633
"attestation": { # Note kind that represents a logical attestation "role" or "authority". For example, an organization might have one `Authority` for "QA" and one for "build". 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't all live in the same project. # A note describing an attestation role.
4633
4634
"hint": { # This submessage provides human-readable hints about the purpose of the authority. 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 "readable" names more suitable for debug output. Note that these hints should not be used to look up authorities in security sensitive contexts, such as when looking up attestations to verify. # Hint hints at the purpose of the attestation authority.
4634
4635
"humanReadableName": "A String", # Required. The human readable name of this attestation authority, for example "qa".
0 commit comments