Skip to content

Commit

Permalink
feat(vpcaccess): update the API
Browse files Browse the repository at this point in the history
#### vpcaccess:v1beta1

The following keys were added:
- schemas.Connector.properties.createTime.description
- schemas.Connector.properties.createTime.format
- schemas.Connector.properties.createTime.readOnly
- schemas.Connector.properties.createTime.type
- schemas.Connector.properties.lastRestartTime.description
- schemas.Connector.properties.lastRestartTime.format
- schemas.Connector.properties.lastRestartTime.readOnly
- schemas.Connector.properties.lastRestartTime.type

The following keys were changed:
- schemas.Connector.properties.maxThroughput.description
- schemas.Connector.properties.minThroughput.description

#### vpcaccess:v1

The following keys were changed:
- schemas.Connector.properties.maxThroughput.description
- schemas.Connector.properties.minThroughput.description
  • Loading branch information
yoshi-automation authored and sofisl committed Jan 3, 2024
1 parent 68a1d5f commit 8db5275
Show file tree
Hide file tree
Showing 4 changed files with 30 additions and 10 deletions.
6 changes: 3 additions & 3 deletions discovery/vpcaccess-v1.json
Original file line number Diff line number Diff line change
Expand Up @@ -384,7 +384,7 @@
}
}
},
"revision": "20230914",
"revision": "20231214",
"rootUrl": "https://vpcaccess.googleapis.com/",
"schemas": {
"Connector": {
Expand Down Expand Up @@ -413,7 +413,7 @@
"type": "integer"
},
"maxThroughput": {
"description": "Maximum throughput of the connector in Mbps. Default is 300, max is 1000. If both max-throughput and max-instances are provided, max-instances takes precedence over max-throughput.",
"description": "Maximum throughput of the connector in Mbps. Refers to the expected throughput when using an `e2-micro` machine type. Value must be a multiple of 100 from 300 through 1000. Must be higher than the value specified by --min-throughput. If both max-throughput and max-instances are provided, max-instances takes precedence over max-throughput. The use of `max-throughput` is discouraged in favor of `max-instances`.",
"format": "int32",
"type": "integer"
},
Expand All @@ -423,7 +423,7 @@
"type": "integer"
},
"minThroughput": {
"description": "Minimum throughput of the connector in Mbps. Default and min is 200. If both min-throughput and min-instances are provided, min-instances takes precedence over min-throughput.",
"description": "Minimum throughput of the connector in Mbps. Refers to the expected throughput when using an `e2-micro` machine type. Value must be a multiple of 100 from 200 through 900. Must be lower than the value specified by --max-throughput. If both min-throughput and min-instances are provided, min-instances takes precedence over min-throughput. The use of `min-throughput` is discouraged in favor of `min-instances`.",
"format": "int32",
"type": "integer"
},
Expand Down
18 changes: 15 additions & 3 deletions discovery/vpcaccess-v1beta1.json
Original file line number Diff line number Diff line change
Expand Up @@ -384,7 +384,7 @@
}
}
},
"revision": "20230914",
"revision": "20231214",
"rootUrl": "https://vpcaccess.googleapis.com/",
"schemas": {
"Connector": {
Expand All @@ -399,10 +399,22 @@
"readOnly": true,
"type": "array"
},
"createTime": {
"description": "Output only. The creation time of the connector.",
"format": "google-datetime",
"readOnly": true,
"type": "string"
},
"ipCidrRange": {
"description": "The range of internal addresses that follows RFC 4632 notation. Example: `10.132.0.0/28`.",
"type": "string"
},
"lastRestartTime": {
"description": "Output only. The last restart time of the connector.",
"format": "google-datetime",
"readOnly": true,
"type": "string"
},
"machineType": {
"description": "Machine type of VM Instance underlying connector. Default is e2-micro",
"type": "string"
Expand All @@ -413,7 +425,7 @@
"type": "integer"
},
"maxThroughput": {
"description": "Maximum throughput of the connector in Mbps. Default is 300, max is 1000. If both max-throughput and max-instances are provided, max-instances takes precedence over max-throughput.",
"description": "Maximum throughput of the connector in Mbps. Refers to the expected throughput when using an `e2-micro` machine type. Value must be a multiple of 100 from 300 through 1000. Must be higher than the value specified by --min-throughput. If both max-throughput and max-instances are provided, max-instances takes precedence over max-throughput. The use of `max-throughput` is discouraged in favor of `max-instances`.",
"format": "int32",
"type": "integer"
},
Expand All @@ -423,7 +435,7 @@
"type": "integer"
},
"minThroughput": {
"description": "Minimum throughput of the connector in Mbps. Default and min is 200. If both min-throughput and min-instances are provided, min-instances takes precedence over min-throughput.",
"description": "Minimum throughput of the connector in Mbps. Refers to the expected throughput when using an `e2-micro` machine type. Value must be a multiple of 100 from 200 through 900. Must be lower than the value specified by --max-throughput. If both min-throughput and min-instances are provided, min-instances takes precedence over min-throughput. The use of `min-throughput` is discouraged in favor of `min-instances`.",
"format": "int32",
"type": "integer"
},
Expand Down
4 changes: 2 additions & 2 deletions src/apis/vpcaccess/v1.ts
Original file line number Diff line number Diff line change
Expand Up @@ -145,15 +145,15 @@ export namespace vpcaccess_v1 {
*/
maxInstances?: number | null;
/**
* Maximum throughput of the connector in Mbps. Default is 300, max is 1000. If both max-throughput and max-instances are provided, max-instances takes precedence over max-throughput.
* Maximum throughput of the connector in Mbps. Refers to the expected throughput when using an `e2-micro` machine type. Value must be a multiple of 100 from 300 through 1000. Must be higher than the value specified by --min-throughput. If both max-throughput and max-instances are provided, max-instances takes precedence over max-throughput. The use of `max-throughput` is discouraged in favor of `max-instances`.
*/
maxThroughput?: number | null;
/**
* Minimum value of instances in autoscaling group underlying the connector.
*/
minInstances?: number | null;
/**
* Minimum throughput of the connector in Mbps. Default and min is 200. If both min-throughput and min-instances are provided, min-instances takes precedence over min-throughput.
* Minimum throughput of the connector in Mbps. Refers to the expected throughput when using an `e2-micro` machine type. Value must be a multiple of 100 from 200 through 900. Must be lower than the value specified by --max-throughput. If both min-throughput and min-instances are provided, min-instances takes precedence over min-throughput. The use of `min-throughput` is discouraged in favor of `min-instances`.
*/
minThroughput?: number | null;
/**
Expand Down
12 changes: 10 additions & 2 deletions src/apis/vpcaccess/v1beta1.ts
Original file line number Diff line number Diff line change
Expand Up @@ -132,10 +132,18 @@ export namespace vpcaccess_v1beta1 {
* Output only. List of projects using the connector.
*/
connectedProjects?: string[] | null;
/**
* Output only. The creation time of the connector.
*/
createTime?: string | null;
/**
* The range of internal addresses that follows RFC 4632 notation. Example: `10.132.0.0/28`.
*/
ipCidrRange?: string | null;
/**
* Output only. The last restart time of the connector.
*/
lastRestartTime?: string | null;
/**
* Machine type of VM Instance underlying connector. Default is e2-micro
*/
Expand All @@ -145,15 +153,15 @@ export namespace vpcaccess_v1beta1 {
*/
maxInstances?: number | null;
/**
* Maximum throughput of the connector in Mbps. Default is 300, max is 1000. If both max-throughput and max-instances are provided, max-instances takes precedence over max-throughput.
* Maximum throughput of the connector in Mbps. Refers to the expected throughput when using an `e2-micro` machine type. Value must be a multiple of 100 from 300 through 1000. Must be higher than the value specified by --min-throughput. If both max-throughput and max-instances are provided, max-instances takes precedence over max-throughput. The use of `max-throughput` is discouraged in favor of `max-instances`.
*/
maxThroughput?: number | null;
/**
* Minimum value of instances in autoscaling group underlying the connector.
*/
minInstances?: number | null;
/**
* Minimum throughput of the connector in Mbps. Default and min is 200. If both min-throughput and min-instances are provided, min-instances takes precedence over min-throughput.
* Minimum throughput of the connector in Mbps. Refers to the expected throughput when using an `e2-micro` machine type. Value must be a multiple of 100 from 200 through 900. Must be lower than the value specified by --max-throughput. If both min-throughput and min-instances are provided, min-instances takes precedence over min-throughput. The use of `min-throughput` is discouraged in favor of `min-instances`.
*/
minThroughput?: number | null;
/**
Expand Down

0 comments on commit 8db5275

Please sign in to comment.