Skip to content

Commit

Permalink
feat(binaryauthorization)!: update the API
Browse files Browse the repository at this point in the history
BREAKING CHANGE: This release has breaking changes.
#### binaryauthorization:v1beta1
The following keys were deleted:
- schemas.Binding.properties.bindingId.type

The following keys were changed:
- schemas.AdmissionWhitelistPattern.properties.namePattern.description

#### binaryauthorization:v1
The following keys were deleted:
- schemas.Binding.properties.bindingId.type
  • Loading branch information
yoshi-automation authored and bcoe committed Nov 17, 2020
1 parent 9a9c727 commit 5a07026
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 12 deletions.
5 changes: 1 addition & 4 deletions discovery/binaryauthorization-v1.json
Original file line number Diff line number Diff line change
Expand Up @@ -522,7 +522,7 @@
}
}
},
"revision": "20201030",
"revision": "20201113",
"rootUrl": "https://binaryauthorization.googleapis.com/",
"schemas": {
"AdmissionRule": {
Expand Down Expand Up @@ -658,9 +658,6 @@
"description": "Associates `members` with a `role`.",
"id": "Binding",
"properties": {
"bindingId": {
"type": "string"
},
"condition": {
"$ref": "Expr",
"description": "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)."
Expand Down
7 changes: 2 additions & 5 deletions discovery/binaryauthorization-v1beta1.json
Original file line number Diff line number Diff line change
Expand Up @@ -522,7 +522,7 @@
}
}
},
"revision": "20201030",
"revision": "20201113",
"rootUrl": "https://binaryauthorization.googleapis.com/",
"schemas": {
"AdmissionRule": {
Expand Down Expand Up @@ -574,7 +574,7 @@
"id": "AdmissionWhitelistPattern",
"properties": {
"namePattern": {
"description": "An image name pattern to allowlist, in the form `registry/path/to/image`. This supports a trailing `*` as a wildcard, but this is allowed only in text after the `registry/` part.",
"description": "An image name pattern to allowlist, in the form `registry/path/to/image`. This supports a trailing `*` as a wildcard, but this is allowed only in text after the `registry/` part. Also wildcards do not match `/`, i.e., gcr.io/nginx* matches gcr.io/nginx@latest, but it does not match gcr.io/nginx/image.",
"type": "string"
}
},
Expand Down Expand Up @@ -658,9 +658,6 @@
"description": "Associates `members` with a `role`.",
"id": "Binding",
"properties": {
"bindingId": {
"type": "string"
},
"condition": {
"$ref": "Expr",
"description": "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)."
Expand Down
1 change: 0 additions & 1 deletion src/apis/binaryauthorization/v1.ts
Original file line number Diff line number Diff line change
Expand Up @@ -212,7 +212,6 @@ export namespace binaryauthorization_v1 {
* Associates `members` with a `role`.
*/
export interface Schema$Binding {
bindingId?: string | null;
/**
* 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).
*/
Expand Down
3 changes: 1 addition & 2 deletions src/apis/binaryauthorization/v1beta1.ts
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ export namespace binaryauthorization_v1beta1 {
*/
export interface Schema$AdmissionWhitelistPattern {
/**
* An image name pattern to allowlist, in the form `registry/path/to/image`. This supports a trailing `*` as a wildcard, but this is allowed only in text after the `registry/` part.
* An image name pattern to allowlist, in the form `registry/path/to/image`. This supports a trailing `*` as a wildcard, but this is allowed only in text after the `registry/` part. Also wildcards do not match `/`, i.e., gcr.io/nginx* matches gcr.io/nginx@latest, but it does not match gcr.io/nginx/image.
*/
namePattern?: string | null;
}
Expand Down Expand Up @@ -212,7 +212,6 @@ export namespace binaryauthorization_v1beta1 {
* Associates `members` with a `role`.
*/
export interface Schema$Binding {
bindingId?: string | null;
/**
* 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).
*/
Expand Down

0 comments on commit 5a07026

Please sign in to comment.