Cloud SQL Admin V1BETA4 API - Class Google::Cloud::Sql::V1beta4::StartWorkloadReplayContext (v0.3.0)

Reference documentation and code samples for the Cloud SQL Admin V1BETA4 API class Google::Cloud::Sql::V1beta4::StartWorkloadReplayContext.

The context for the StartWorkloadReplay operation, which contains details about starting the execution of a captured workload (recorded read and write SQL queries) on a replay instance (the Cloud SQL instance where the recorded SQL queries are executed).

Inherits

  • Object

Extended By

  • Google::Protobuf::MessageExts::ClassMethods

Includes

  • Google::Protobuf::MessageExts

Methods

#replay_instance

def replay_instance() -> ::String
Returns
  • (::String) — Required. The name of the Cloud SQL instance where the captured workload (SQL queries) is being executed, excluding the project ID (for example, my-replay-instance). The instance name must start with a lowercase letter and contain only lowercase letters, numbers, and hyphens. The combined length of project-ID:instance-name must be 98 characters or less.

#replay_instance=

def replay_instance=(value) -> ::String
Parameter
  • value (::String) — Required. The name of the Cloud SQL instance where the captured workload (SQL queries) is being executed, excluding the project ID (for example, my-replay-instance). The instance name must start with a lowercase letter and contain only lowercase letters, numbers, and hyphens. The combined length of project-ID:instance-name must be 98 characters or less.
Returns
  • (::String) — Required. The name of the Cloud SQL instance where the captured workload (SQL queries) is being executed, excluding the project ID (for example, my-replay-instance). The instance name must start with a lowercase letter and contain only lowercase letters, numbers, and hyphens. The combined length of project-ID:instance-name must be 98 characters or less.

#workload_id

def workload_id() -> ::String
Returns
  • (::String) — Output only. The ID of the workload to start executing on the replay instance. Each workload capture generates a unique ID in the format workload-<epoch_timestamp> (for example, workload-1786046400). Use this ID to start executing the recorded SQL queries.