API Reference google_api_os_config v0.12.1

Modules

API client metadata for GoogleApi.OSConfig.V1.

API calls for all endpoints tagged Operations.

API calls for all endpoints tagged Projects.

Handle Tesla connections for GoogleApi.OSConfig.V1.

Apt patching is completed by executing apt-get update && apt-get upgrade. Additional options can be set to control how this is executed.

Message for canceling a patch job.

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); } The JSON representation for Empty is empty JSON object {}.

A step that runs an executable for a PatchJob.

Common configurations for an ExecStep.

A request message to initiate patching across Compute Engine instances.

Message encapsulating a value that can be either absolute ("fixed") or relative ("percent") to a value.

Cloud Storage object representation.

Googet patching is performed by running googet update.

The inventory details of a VM.

A single piece of inventory on a VM.

Operating system information for the VM.

Software package information of the operating system.

Information related to the a standard versioned package. This includes package info for APT, Yum, Zypper, and Googet package managers.

Information related to a Quick Fix Engineering package. Fields are taken from Windows QuickFixEngineering Interface and match the source names: https://docs.microsoft.com/en-us/windows/win32/cimwin32prov/win32-quickfixengineering

Details related to a Windows Update package. Field data and names are taken from Windows Update API IUpdate Interface: https://docs.microsoft.com/en-us/windows/win32/api/_wua/ Descriptive fields like title, and description are localized based on the locale of the VM being updated.

Details related to a Zypper Patch.

The response message for Operations.ListOperations.

A response message for listing patch deployments.

A response message for listing the instances details for a patch job.

A response message for listing patch jobs.

Represents a monthly schedule. An example of a valid monthly schedule is "on the third Tuesday of the month" or "on the 15th of the month".

OS policy assignment operation metadata provided by OS policy assignment API methods that return long running operations.

Sets the time for a one time patch deployment. Timestamp is in RFC3339 text format.

This resource represents a long-running operation that is the result of a network API call.

Patch configuration specifications. Contains details on how to apply the patch(es) to a VM instance.

Patch deployments are configurations that individual patch jobs use to complete a patch. These configurations include instance filter, package repository settings, and a schedule. For more information about creating and managing patch deployments, see Scheduling patch jobs.

A filter to target VM instances for patching. The targeted VMs must meet all criteria specified. So if both labels and zones are specified, the patch job targets only VMs with those labels and in those zones.

Targets a group of VM instances by using their assigned labels. Labels are key-value pairs. A GroupLabel is a combination of labels that is used to target VMs for a patch job. For example, a patch job can target VMs that have the following GroupLabel: {"env":"test", "app":"web"}. This means that the patch job is applied to VMs that have both the labels env=test and app=web.

A high level representation of a patch job that is either in progress or has completed. Instance details are not included in the job. To paginate through instance details, use ListPatchJobInstanceDetails. For more information about patch jobs, see Creating patch jobs.

Patch details for a VM instance. For more information about reviewing VM instance details, see Listing all VM instance details for a specific patch job.

A summary of the current patch state across all instances that this patch job affects. Contains counts of instances in different states. These states map to InstancePatchState. List patch job instance details to see the specific states of each instance.

Patch rollout configuration specifications. Contains details on the concurrency control when applying patch(es) to all targeted VMs.

Sets the time for recurring patch deployments.

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

Represents a time of day. The date and time zone are either not significant or are specified elsewhere. An API may choose to allow leap seconds. Related types are google.type.Date and google.protobuf.Timestamp.

Represents one week day in a month. An example is "the 4th Sunday".

Represents a weekly schedule.

Windows patching is performed using the Windows Update Agent.

Yum patching is performed by executing yum update. Additional options can be set to control how this is executed. Note that not all settings are supported on all platforms.

Zypper patching is performed by running zypper patch. See also https://en.opensuse.org/SDB:Zypper_manual.