Skip to content

Commit

Permalink
feat(ondemandscanning): update the api
Browse files Browse the repository at this point in the history
#### ondemandscanning:v1

The following keys were added:
- schemas.ComplianceOccurrence (Total Keys: 5)
- schemas.NonCompliantFile (Total Keys: 5)
- schemas.Occurrence.properties.compliance.$ref (Total Keys: 1)

#### ondemandscanning:v1beta1

The following keys were added:
- schemas.ComplianceOccurrence (Total Keys: 5)
- schemas.NonCompliantFile (Total Keys: 5)
- schemas.Occurrence.properties.compliance.$ref (Total Keys: 1)
  • Loading branch information
yoshi-automation committed May 27, 2021
1 parent 65ab8cf commit b77d12d
Show file tree
Hide file tree
Showing 4 changed files with 100 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -244,6 +244,16 @@ <h3>Method Details</h3>
},
&quot;provenanceBytes&quot;: &quot;A String&quot;, # Serialized JSON representation of the provenance, used in generating the build signature in the corresponding build note. After verifying the signature, `provenance_bytes` can be unmarshalled and compared to the provenance to confirm that it is unchanged. A base64-encoded string representation of the provenance bytes is used for the signature in order to interoperate with openssl which expects this format for signature verification. The serialized form is captured both to avoid ambiguity in how the provenance is marshalled to json as well to prevent incompatibilities with future changes.
},
&quot;compliance&quot;: { # An indication that the compliance checks in the associated ComplianceNote were not satisfied for particular resources or a specified reason. # Describes a compliance violation on a linked resource.
&quot;nonComplianceReason&quot;: &quot;A String&quot;,
&quot;nonCompliantFiles&quot;: [
{ # Details about files that caused a compliance check to fail.
&quot;displayCommand&quot;: &quot;A String&quot;, # Command to display the non-compliant files.
&quot;path&quot;: &quot;A String&quot;, # display_command is a single command that can be used to display a list of non compliant files. When there is no such command, we can also iterate a list of non compliant file using &#x27;path&#x27;. Empty if `display_command` is set.
&quot;reason&quot;: &quot;A String&quot;, # Explains why a file is non compliant for a CIS check.
},
],
},
&quot;createTime&quot;: &quot;A String&quot;, # Output only. The time this occurrence was created.
&quot;deployment&quot;: { # The period during which some deployable was active in a runtime. # Describes the deployment of an artifact on a runtime.
&quot;address&quot;: &quot;A String&quot;, # Address of the runtime element hosting this deployment.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -244,6 +244,16 @@ <h3>Method Details</h3>
},
&quot;provenanceBytes&quot;: &quot;A String&quot;, # Serialized JSON representation of the provenance, used in generating the build signature in the corresponding build note. After verifying the signature, `provenance_bytes` can be unmarshalled and compared to the provenance to confirm that it is unchanged. A base64-encoded string representation of the provenance bytes is used for the signature in order to interoperate with openssl which expects this format for signature verification. The serialized form is captured both to avoid ambiguity in how the provenance is marshalled to json as well to prevent incompatibilities with future changes.
},
&quot;compliance&quot;: { # An indication that the compliance checks in the associated ComplianceNote were not satisfied for particular resources or a specified reason. # Describes a compliance violation on a linked resource.
&quot;nonComplianceReason&quot;: &quot;A String&quot;,
&quot;nonCompliantFiles&quot;: [
{ # Details about files that caused a compliance check to fail.
&quot;displayCommand&quot;: &quot;A String&quot;, # Command to display the non-compliant files.
&quot;path&quot;: &quot;A String&quot;, # display_command is a single command that can be used to display a list of non compliant files. When there is no such command, we can also iterate a list of non compliant file using &#x27;path&#x27;. Empty if `display_command` is set.
&quot;reason&quot;: &quot;A String&quot;, # Explains why a file is non compliant for a CIS check.
},
],
},
&quot;createTime&quot;: &quot;A String&quot;, # Output only. The time this occurrence was created.
&quot;deployment&quot;: { # The period during which some deployable was active in a runtime. # Describes the deployment of an artifact on a runtime.
&quot;address&quot;: &quot;A String&quot;, # Address of the runtime element hosting this deployment.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -339,7 +339,7 @@
}
}
},
"revision": "20210508",
"revision": "20210524",
"rootUrl": "https://ondemandscanning.googleapis.com/",
"schemas": {
"AliasContext": {
Expand Down Expand Up @@ -649,6 +649,22 @@
},
"type": "object"
},
"ComplianceOccurrence": {
"description": "An indication that the compliance checks in the associated ComplianceNote were not satisfied for particular resources or a specified reason.",
"id": "ComplianceOccurrence",
"properties": {
"nonComplianceReason": {
"type": "string"
},
"nonCompliantFiles": {
"items": {
"$ref": "NonCompliantFile"
},
"type": "array"
}
},
"type": "object"
},
"DeploymentOccurrence": {
"description": "The period during which some deployable was active in a runtime.",
"id": "DeploymentOccurrence",
Expand Down Expand Up @@ -974,6 +990,25 @@
},
"type": "object"
},
"NonCompliantFile": {
"description": "Details about files that caused a compliance check to fail.",
"id": "NonCompliantFile",
"properties": {
"displayCommand": {
"description": "Command to display the non-compliant files.",
"type": "string"
},
"path": {
"description": "display_command is a single command that can be used to display a list of non compliant files. When there is no such command, we can also iterate a list of non compliant file using 'path'. Empty if `display_command` is set.",
"type": "string"
},
"reason": {
"description": "Explains why a file is non compliant for a CIS check.",
"type": "string"
}
},
"type": "object"
},
"Occurrence": {
"description": "An instance of an analysis type that has been found on a resource.",
"id": "Occurrence",
Expand All @@ -986,6 +1021,10 @@
"$ref": "BuildOccurrence",
"description": "Describes a verifiable build."
},
"compliance": {
"$ref": "ComplianceOccurrence",
"description": "Describes a compliance violation on a linked resource."
},
"createTime": {
"description": "Output only. The time this occurrence was created.",
"format": "google-datetime",
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -339,7 +339,7 @@
}
}
},
"revision": "20210508",
"revision": "20210524",
"rootUrl": "https://ondemandscanning.googleapis.com/",
"schemas": {
"AliasContext": {
Expand Down Expand Up @@ -649,6 +649,22 @@
},
"type": "object"
},
"ComplianceOccurrence": {
"description": "An indication that the compliance checks in the associated ComplianceNote were not satisfied for particular resources or a specified reason.",
"id": "ComplianceOccurrence",
"properties": {
"nonComplianceReason": {
"type": "string"
},
"nonCompliantFiles": {
"items": {
"$ref": "NonCompliantFile"
},
"type": "array"
}
},
"type": "object"
},
"DeploymentOccurrence": {
"description": "The period during which some deployable was active in a runtime.",
"id": "DeploymentOccurrence",
Expand Down Expand Up @@ -974,6 +990,25 @@
},
"type": "object"
},
"NonCompliantFile": {
"description": "Details about files that caused a compliance check to fail.",
"id": "NonCompliantFile",
"properties": {
"displayCommand": {
"description": "Command to display the non-compliant files.",
"type": "string"
},
"path": {
"description": "display_command is a single command that can be used to display a list of non compliant files. When there is no such command, we can also iterate a list of non compliant file using 'path'. Empty if `display_command` is set.",
"type": "string"
},
"reason": {
"description": "Explains why a file is non compliant for a CIS check.",
"type": "string"
}
},
"type": "object"
},
"Occurrence": {
"description": "An instance of an analysis type that has been found on a resource.",
"id": "Occurrence",
Expand All @@ -986,6 +1021,10 @@
"$ref": "BuildOccurrence",
"description": "Describes a verifiable build."
},
"compliance": {
"$ref": "ComplianceOccurrence",
"description": "Describes a compliance violation on a linked resource."
},
"createTime": {
"description": "Output only. The time this occurrence was created.",
"format": "google-datetime",
Expand Down

0 comments on commit b77d12d

Please sign in to comment.