feat(run): update the api

#### run:v1 The following keys were added: - schemas.GoogleDevtoolsCloudbuildV1ApprovalConfig (Total Keys: 3) - schemas.GoogleDevtoolsCloudbuildV1ApprovalResult (Total Keys: 9) - schemas.GoogleDevtoolsCloudbuildV1ArtifactObjects (Total Keys: 7) - schemas.GoogleDevtoolsCloudbuildV1Artifacts (Total Keys: 11) - schemas.GoogleDevtoolsCloudbuildV1Build (Total Keys: 124) - schemas.GoogleDevtoolsCloudbuildV1BuiltImage (Total Keys: 6) - schemas.GoogleDevtoolsCloudbuildV1ConnectedRepository (Total Keys: 4) - schemas.GoogleDevtoolsCloudbuildV1FailureInfo (Total Keys: 4) - schemas.GoogleDevtoolsCloudbuildV1FileHashes (Total Keys: 4) - schemas.GoogleDevtoolsCloudbuildV1GitSource (Total Keys: 3) - schemas.GoogleDevtoolsCloudbuildV1Hash (Total Keys: 5) - schemas.GoogleDevtoolsCloudbuildV1InlineSecret (Total Keys: 6) - schemas.GoogleDevtoolsCloudbuildV1MavenArtifact (Total Keys: 7) - schemas.GoogleDevtoolsCloudbuildV1NpmPackage (Total Keys: 4) - schemas.GoogleDevtoolsCloudbuildV1PoolOption (Total Keys: 3) - schemas.GoogleDevtoolsCloudbuildV1PythonPackage (Total Keys: 5) - schemas.GoogleDevtoolsCloudbuildV1RepoSource (Total Keys: 11) - schemas.GoogleDevtoolsCloudbuildV1Results (Total Keys: 19) - schemas.GoogleDevtoolsCloudbuildV1Secret (Total Keys: 16) - schemas.GoogleDevtoolsCloudbuildV1Source (Total Keys: 19) - schemas.GoogleDevtoolsCloudbuildV1StorageSource (Total Keys: 13) - schemas.GoogleDevtoolsCloudbuildV1TimeSpan (Total Keys: 6) - schemas.GoogleDevtoolsCloudbuildV1UploadedMavenArtifact (Total Keys: 6) - schemas.GoogleDevtoolsCloudbuildV1UploadedNpmPackage (Total Keys: 6) - schemas.GoogleDevtoolsCloudbuildV1UploadedPythonPackage (Total Keys: 6) - schemas.GoogleDevtoolsCloudbuildV1Volume (Total Keys: 4) - schemas.GoogleDevtoolsCloudbuildV1Warning (Total Keys: 4) #### run:v2 The following keys were added: - schemas.GoogleDevtoolsCloudbuildV1ApprovalConfig (Total Keys: 3) - schemas.GoogleDevtoolsCloudbuildV1ApprovalResult (Total Keys: 9) - schemas.GoogleDevtoolsCloudbuildV1ArtifactObjects (Total Keys: 7) - schemas.GoogleDevtoolsCloudbuildV1Artifacts (Total Keys: 11) - schemas.GoogleDevtoolsCloudbuildV1Build (Total Keys: 124) - schemas.GoogleDevtoolsCloudbuildV1BuiltImage (Total Keys: 6) - schemas.GoogleDevtoolsCloudbuildV1ConnectedRepository (Total Keys: 4) - schemas.GoogleDevtoolsCloudbuildV1FailureInfo (Total Keys: 4) - schemas.GoogleDevtoolsCloudbuildV1FileHashes (Total Keys: 4) - schemas.GoogleDevtoolsCloudbuildV1GitSource (Total Keys: 3) - schemas.GoogleDevtoolsCloudbuildV1Hash (Total Keys: 5) - schemas.GoogleDevtoolsCloudbuildV1InlineSecret (Total Keys: 6) - schemas.GoogleDevtoolsCloudbuildV1MavenArtifact (Total Keys: 7) - schemas.GoogleDevtoolsCloudbuildV1NpmPackage (Total Keys: 4) - schemas.GoogleDevtoolsCloudbuildV1PoolOption (Total Keys: 3) - schemas.GoogleDevtoolsCloudbuildV1PythonPackage (Total Keys: 5) - schemas.GoogleDevtoolsCloudbuildV1RepoSource (Total Keys: 11) - schemas.GoogleDevtoolsCloudbuildV1Results (Total Keys: 19) - schemas.GoogleDevtoolsCloudbuildV1Secret (Total Keys: 16) - schemas.GoogleDevtoolsCloudbuildV1Source (Total Keys: 19) - schemas.GoogleDevtoolsCloudbuildV1StorageSource (Total Keys: 13) - schemas.GoogleDevtoolsCloudbuildV1TimeSpan (Total Keys: 6) - schemas.GoogleDevtoolsCloudbuildV1UploadedMavenArtifact (Total Keys: 6) - schemas.GoogleDevtoolsCloudbuildV1UploadedNpmPackage (Total Keys: 6) - schemas.GoogleDevtoolsCloudbuildV1UploadedPythonPackage (Total Keys: 6) - schemas.GoogleDevtoolsCloudbuildV1Volume (Total Keys: 4) - schemas.GoogleDevtoolsCloudbuildV1Warning (Total Keys: 4)
googleapis · Mar 12, 2024 · 59e07c8 · 59e07c8
1 parent c9e8468
commit 59e07c8
Show file tree

Hide file tree

Showing 3 changed files with 2,551 additions and 7 deletions.
diff --git a/docs/dyn/run_v2.projects.locations.services.html b/docs/dyn/run_v2.projects.locations.services.html
@@ -170,7 +170,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;minInstanceCount&quot;: 42, # 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. (ALPHA)
+    &quot;minInstanceCount&quot;: 42, # 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. (BETA)
   },
   &quot;template&quot;: { # RevisionTemplate describes the data a revision should have when created from a template. # Required. The template used to create revisions for this Service.
     &quot;annotations&quot;: { # Unstructured key value map that may be set by external tools to store and arbitrary metadata. They are not queryable and should be preserved when modifying objects. Cloud Run API v2 does not support annotations with `run.googleapis.com`, `cloud.googleapis.com`, `serving.knative.dev`, or `autoscaling.knative.dev` namespaces, and they will be rejected. All system annotations in v1 now have a corresponding field in v2 RevisionTemplate. This field follows Kubernetes annotations&#x27; namespacing, limits, and rules.
@@ -492,7 +492,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;minInstanceCount&quot;: 42, # 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. (ALPHA)
+    &quot;minInstanceCount&quot;: 42, # 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. (BETA)
   },
   &quot;template&quot;: { # RevisionTemplate describes the data a revision should have when created from a template. # Required. The template used to create revisions for this Service.
     &quot;annotations&quot;: { # Unstructured key value map that may be set by external tools to store and arbitrary metadata. They are not queryable and should be preserved when modifying objects. Cloud Run API v2 does not support annotations with `run.googleapis.com`, `cloud.googleapis.com`, `serving.knative.dev`, or `autoscaling.knative.dev` namespaces, and they will be rejected. All system annotations in v1 now have a corresponding field in v2 RevisionTemplate. This field follows Kubernetes annotations&#x27; namespacing, limits, and rules.
@@ -801,7 +801,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;minInstanceCount&quot;: 42, # 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. (ALPHA)
+        &quot;minInstanceCount&quot;: 42, # 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. (BETA)
       },
       &quot;template&quot;: { # RevisionTemplate describes the data a revision should have when created from a template. # Required. The template used to create revisions for this Service.
         &quot;annotations&quot;: { # Unstructured key value map that may be set by external tools to store and arbitrary metadata. They are not queryable and should be preserved when modifying objects. Cloud Run API v2 does not support annotations with `run.googleapis.com`, `cloud.googleapis.com`, `serving.knative.dev`, or `autoscaling.knative.dev` namespaces, and they will be rejected. All system annotations in v1 now have a corresponding field in v2 RevisionTemplate. This field follows Kubernetes annotations&#x27; namespacing, limits, and rules.
@@ -1067,7 +1067,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;minInstanceCount&quot;: 42, # 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. (ALPHA)
+    &quot;minInstanceCount&quot;: 42, # 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. (BETA)
   },
   &quot;template&quot;: { # RevisionTemplate describes the data a revision should have when created from a template. # Required. The template used to create revisions for this Service.
     &quot;annotations&quot;: { # Unstructured key value map that may be set by external tools to store and arbitrary metadata. They are not queryable and should be preserved when modifying objects. Cloud Run API v2 does not support annotations with `run.googleapis.com`, `cloud.googleapis.com`, `serving.knative.dev`, or `autoscaling.knative.dev` namespaces, and they will be rejected. All system annotations in v1 now have a corresponding field in v2 RevisionTemplate. This field follows Kubernetes annotations&#x27; namespacing, limits, and rules.