feat: Automated regeneration of ToolResults client

clients/tool_results/lib/google_api/tool_results/v1beta3/api/projects.ex

@@ -1553,7 +1553,7 @@ defmodule GoogleApi.ToolResults.V1beta3.Api.Projects do
   end
 
   @doc """
-  Publish xml files to an existing Step. May return any of the following canonical error codes: - PERMISSION_DENIED - if the user is not authorized to write project - INVALID_ARGUMENT - if the request is malformed - FAILED_PRECONDITION - if the requested state transition is illegal, e.g try to upload a duplicate xml file or a file too large. - NOT_FOUND - if the containing Execution does not exist
+  Publish xml files to an existing Step. May return any of the following canonical error codes: - PERMISSION_DENIED - if the user is not authorized to write project - INVALID_ARGUMENT - if the request is malformed - FAILED_PRECONDITION - if the requested state transition is illegal, e.g. try to upload a duplicate xml file or a file too large. - NOT_FOUND - if the containing Execution does not exist
 
   ## Parameters
 

clients/tool_results/lib/google_api/tool_results/v1beta3/metadata.ex

@@ -20,7 +20,7 @@ defmodule GoogleApi.ToolResults.V1beta3 do
   API client metadata for GoogleApi.ToolResults.V1beta3.
   """
 
-  @discovery_revision "20220808"
+  @discovery_revision "20240311"
 
   def discovery_revision(), do: @discovery_revision
 end

clients/tool_results/lib/google_api/tool_results/v1beta3/model/asset_issue.ex

@@ -0,0 +1,41 @@
+# Copyright 2019 Google LLC
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+# NOTE: This file is auto generated by the elixir code generator program.
+# Do not edit this file manually.
+
+defmodule GoogleApi.ToolResults.V1beta3.Model.AssetIssue do
+  @moduledoc """
+  There was an issue with the assets in this test.
+
+  ## Attributes
+
+  """
+
+  use GoogleApi.Gax.ModelBase
+
+  @type t :: %__MODULE__{}
+end
+
+defimpl Poison.Decoder, for: GoogleApi.ToolResults.V1beta3.Model.AssetIssue do
+  def decode(value, options) do
+    GoogleApi.ToolResults.V1beta3.Model.AssetIssue.decode(value, options)
+  end
+end
+
+defimpl Poison.Encoder, for: GoogleApi.ToolResults.V1beta3.Model.AssetIssue do
+  def encode(value, options) do
+    GoogleApi.Gax.ModelBase.encode(value, options)
+  end
+end

clients/tool_results/lib/google_api/tool_results/v1beta3/model/failed_to_install.ex

@@ -17,7 +17,7 @@
 
 defmodule GoogleApi.ToolResults.V1beta3.Model.FailedToInstall do
   @moduledoc """
-  Failed to install the APK.
+  Failed to install the App.
 
   ## Attributes
 

clients/tool_results/lib/google_api/tool_results/v1beta3/model/step.ex

@@ -17,7 +17,7 @@
 
 defmodule GoogleApi.ToolResults.V1beta3.Model.Step do
   @moduledoc """
-  A Step represents a single operation performed as part of Execution. A step can be used to represent the execution of a tool ( for example a test runner execution or an execution of a compiler). Steps can overlap (for instance two steps might have the same start time if some operations are done in parallel). Here is an example, let's consider that we have a continuous build is executing a test runner for each iteration. The workflow would look like: - user creates a Execution with id 1 - user creates an TestExecutionStep with id 100 for Execution 1 - user update TestExecutionStep with id 100 to add a raw xml log + the service parses the xml logs and returns a TestExecutionStep with updated TestResult(s). - user update the status of TestExecutionStep with id 100 to COMPLETE A Step can be updated until its state is set to COMPLETE at which points it becomes immutable. Next tag: 27
+  A Step represents a single operation performed as part of Execution. A step can be used to represent the execution of a tool ( for example a test runner execution or an execution of a compiler). Steps can overlap (for instance two steps might have the same start time if some operations are done in parallel). Here is an example, let's consider that we have a continuous build is executing a test runner for each iteration. The workflow would look like: - user creates a Execution with id 1 - user creates a TestExecutionStep with id 100 for Execution 1 - user update TestExecutionStep with id 100 to add a raw xml log + the service parses the xml logs and returns a TestExecutionStep with updated TestResult(s). - user update the status of TestExecutionStep with id 100 to COMPLETE A Step can be updated until its state is set to COMPLETE at which points it becomes immutable.
 
   ## Attributes