Skip to content

Commit

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

The following keys were added:
- schemas.GoogleCloudRunV2ServiceScaling.properties.manualInstanceCount (Total Keys: 2)
  • Loading branch information
yoshi-automation committed Dec 17, 2024
1 parent 8f7e7cd commit 024a0ec
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 1 deletion.
4 changes: 4 additions & 0 deletions docs/dyn/run_v2.projects.locations.services.html
Original file line number Diff line number Diff line change
Expand Up @@ -172,6 +172,7 @@ <h3>Method Details</h3>
&quot;reconciling&quot;: True or False, # Output only. Returns true if the Service is currently being acted upon by the system to bring it into the desired state. When a new Service is created, or an existing one is updated, Cloud Run will asynchronously perform all necessary steps to bring the Service to the desired serving state. This process is called reconciliation. While reconciliation is in process, `observed_generation`, `latest_ready_revison`, `traffic_statuses`, and `uri` will have transient values that might mismatch the intended state: Once reconciliation is over (and this field is false), there are two possible outcomes: reconciliation succeeded and the serving state matches the Service, or there was an error, and reconciliation failed. This state can be found in `terminal_condition.state`. If reconciliation succeeded, the following fields will match: `traffic` and `traffic_statuses`, `observed_generation` and `generation`, `latest_ready_revision` and `latest_created_revision`. If reconciliation failed, `traffic_statuses`, `observed_generation`, and `latest_ready_revision` will have the state of the last serving revision, or empty for newly created Services. Additional information on the failure can be found in `terminal_condition` and `conditions`.
&quot;satisfiesPzs&quot;: True or False, # Output only. Reserved for future use.
&quot;scaling&quot;: { # Scaling settings applied at the service level rather than at the revision level. # Optional. Specifies service-level scaling settings
&quot;manualInstanceCount&quot;: 42, # Optional. total instance count for the service in manual scaling mode. This number of instances is divided among all revisions with specified traffic based on the percent of traffic they are receiving.
&quot;minInstanceCount&quot;: 42, # Optional. total min instances for the service. This number of instances is divided among all revisions with specified traffic based on the percent of traffic they are receiving.
&quot;scalingMode&quot;: &quot;A String&quot;, # Optional. The scaling mode for the service.
},
Expand Down Expand Up @@ -511,6 +512,7 @@ <h3>Method Details</h3>
&quot;reconciling&quot;: True or False, # Output only. Returns true if the Service is currently being acted upon by the system to bring it into the desired state. When a new Service is created, or an existing one is updated, Cloud Run will asynchronously perform all necessary steps to bring the Service to the desired serving state. This process is called reconciliation. While reconciliation is in process, `observed_generation`, `latest_ready_revison`, `traffic_statuses`, and `uri` will have transient values that might mismatch the intended state: Once reconciliation is over (and this field is false), there are two possible outcomes: reconciliation succeeded and the serving state matches the Service, or there was an error, and reconciliation failed. This state can be found in `terminal_condition.state`. If reconciliation succeeded, the following fields will match: `traffic` and `traffic_statuses`, `observed_generation` and `generation`, `latest_ready_revision` and `latest_created_revision`. If reconciliation failed, `traffic_statuses`, `observed_generation`, and `latest_ready_revision` will have the state of the last serving revision, or empty for newly created Services. Additional information on the failure can be found in `terminal_condition` and `conditions`.
&quot;satisfiesPzs&quot;: True or False, # Output only. Reserved for future use.
&quot;scaling&quot;: { # Scaling settings applied at the service level rather than at the revision level. # Optional. Specifies service-level scaling settings
&quot;manualInstanceCount&quot;: 42, # Optional. total instance count for the service in manual scaling mode. This number of instances is divided among all revisions with specified traffic based on the percent of traffic they are receiving.
&quot;minInstanceCount&quot;: 42, # Optional. total min instances for the service. This number of instances is divided among all revisions with specified traffic based on the percent of traffic they are receiving.
&quot;scalingMode&quot;: &quot;A String&quot;, # Optional. The scaling mode for the service.
},
Expand Down Expand Up @@ -837,6 +839,7 @@ <h3>Method Details</h3>
&quot;reconciling&quot;: True or False, # Output only. Returns true if the Service is currently being acted upon by the system to bring it into the desired state. When a new Service is created, or an existing one is updated, Cloud Run will asynchronously perform all necessary steps to bring the Service to the desired serving state. This process is called reconciliation. While reconciliation is in process, `observed_generation`, `latest_ready_revison`, `traffic_statuses`, and `uri` will have transient values that might mismatch the intended state: Once reconciliation is over (and this field is false), there are two possible outcomes: reconciliation succeeded and the serving state matches the Service, or there was an error, and reconciliation failed. This state can be found in `terminal_condition.state`. If reconciliation succeeded, the following fields will match: `traffic` and `traffic_statuses`, `observed_generation` and `generation`, `latest_ready_revision` and `latest_created_revision`. If reconciliation failed, `traffic_statuses`, `observed_generation`, and `latest_ready_revision` will have the state of the last serving revision, or empty for newly created Services. Additional information on the failure can be found in `terminal_condition` and `conditions`.
&quot;satisfiesPzs&quot;: True or False, # Output only. Reserved for future use.
&quot;scaling&quot;: { # Scaling settings applied at the service level rather than at the revision level. # Optional. Specifies service-level scaling settings
&quot;manualInstanceCount&quot;: 42, # Optional. total instance count for the service in manual scaling mode. This number of instances is divided among all revisions with specified traffic based on the percent of traffic they are receiving.
&quot;minInstanceCount&quot;: 42, # Optional. total min instances for the service. This number of instances is divided among all revisions with specified traffic based on the percent of traffic they are receiving.
&quot;scalingMode&quot;: &quot;A String&quot;, # Optional. The scaling mode for the service.
},
Expand Down Expand Up @@ -1120,6 +1123,7 @@ <h3>Method Details</h3>
&quot;reconciling&quot;: True or False, # Output only. Returns true if the Service is currently being acted upon by the system to bring it into the desired state. When a new Service is created, or an existing one is updated, Cloud Run will asynchronously perform all necessary steps to bring the Service to the desired serving state. This process is called reconciliation. While reconciliation is in process, `observed_generation`, `latest_ready_revison`, `traffic_statuses`, and `uri` will have transient values that might mismatch the intended state: Once reconciliation is over (and this field is false), there are two possible outcomes: reconciliation succeeded and the serving state matches the Service, or there was an error, and reconciliation failed. This state can be found in `terminal_condition.state`. If reconciliation succeeded, the following fields will match: `traffic` and `traffic_statuses`, `observed_generation` and `generation`, `latest_ready_revision` and `latest_created_revision`. If reconciliation failed, `traffic_statuses`, `observed_generation`, and `latest_ready_revision` will have the state of the last serving revision, or empty for newly created Services. Additional information on the failure can be found in `terminal_condition` and `conditions`.
&quot;satisfiesPzs&quot;: True or False, # Output only. Reserved for future use.
&quot;scaling&quot;: { # Scaling settings applied at the service level rather than at the revision level. # Optional. Specifies service-level scaling settings
&quot;manualInstanceCount&quot;: 42, # Optional. total instance count for the service in manual scaling mode. This number of instances is divided among all revisions with specified traffic based on the percent of traffic they are receiving.
&quot;minInstanceCount&quot;: 42, # Optional. total min instances for the service. This number of instances is divided among all revisions with specified traffic based on the percent of traffic they are receiving.
&quot;scalingMode&quot;: &quot;A String&quot;, # Optional. The scaling mode for the service.
},
Expand Down
7 changes: 6 additions & 1 deletion googleapiclient/discovery_cache/documents/run.v2.json
Original file line number Diff line number Diff line change
Expand Up @@ -1526,7 +1526,7 @@
}
}
},
"revision": "20241115",
"revision": "20241206",
"rootUrl": "https://run.googleapis.com/",
"schemas": {
"GoogleCloudRunV2BinaryAuthorization": {
Expand Down Expand Up @@ -3428,6 +3428,11 @@
"description": "Scaling settings applied at the service level rather than at the revision level.",
"id": "GoogleCloudRunV2ServiceScaling",
"properties": {
"manualInstanceCount": {
"description": "Optional. total instance count for the service in manual scaling mode. This number of instances is divided among all revisions with specified traffic based on the percent of traffic they are receiving.",
"format": "int32",
"type": "integer"
},
"minInstanceCount": {
"description": "Optional. total min instances for the service. This number of instances is divided among all revisions with specified traffic based on the percent of traffic they are receiving.",
"format": "int32",
Expand Down

0 comments on commit 024a0ec

Please sign in to comment.