google_api_cloud_iot v0.5.0 API Reference

Modules

API calls for all endpoints tagged Projects.

Handle Tesla connections for GoogleApi.CloudIot.V1.

Helper functions for deserializing responses into models.

Request for `BindDeviceToGateway`.

Response for `BindDeviceToGateway`.

Associates `members` with a `role`.

The device resource.

The device configuration. Eventually delivered to devices.

A server-stored device credential used for authentication.

A container for a group of devices.

The device state, as reported by the device.

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 `{}`.

The configuration for forwarding telemetry events.

Represents an expression text. Example: title: "User account presence" description: "Determines whether the request has a user account" expression: "size(request.user) > 0"

Gateway-related configuration and state.

Request message for `GetIamPolicy` method.

The configuration of the HTTP bridge for a device registry.

Response for `ListDeviceConfigVersions`.

Response for `ListDeviceRegistries`.

Response for `ListDeviceStates`.

Request for `ModifyCloudToDeviceConfig`.

The configuration of MQTT for a device registry.

Defines an Identity and Access Management (IAM) policy. It is used to specify access control policies for Cloud Platform resources. A `Policy` consists of a list of `bindings`. A `binding` binds a list of `members` to a `role`, where the members can be user accounts, Google groups, Google domains, and service accounts. A `role` is a named list of permissions defined by IAM. JSON Example { "bindings": [ { "role": "roles/owner", "members": [ "user:mike@example.com", "group:admins@example.com", "domain:google.com", "serviceAccount:my-other-app@appspot.gserviceaccount.com" ] }, { "role": "roles/viewer", "members": ["user:sean@example.com"] } ] } YAML Example bindings: - members: - user:mike@example.com - group:admins@example.com - domain:google.com - serviceAccount:my-other-app@appspot.gserviceaccount.com role: roles/owner - members: - user:sean@example.com role: roles/viewer For a description of IAM and its features, see the IAM developer's guide.

A public key certificate format and data.

A public key format and data.

A server-stored registry credential used to validate device credentials.

Request for `SendCommandToDevice`.

Response for `SendCommandToDevice`.

Request message for `SetIamPolicy` method.

The configuration for notification of new states received from the device.

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. The error model is designed to be: - Simple to use and understand for most users - Flexible enough to meet unexpected needs # Overview The `Status` message contains three pieces of data: error code, error message, and error details. The error code should be an enum value of google.rpc.Code, but it may accept additional error codes if needed. The error message should be a developer-facing English message that helps developers understand and resolve the error. If a localized user-facing error message is needed, put the localized message in the error details or localize it in the client. The optional error details may contain arbitrary information about the error. There is a predefined set of error detail types in the package `google.rpc` that can be used for common error conditions. # Language mapping The `Status` message is the logical representation of the error model, but it is not necessarily the actual wire format. When the `Status` message is exposed in different client libraries and different wire protocols, it can be mapped differently. For example, it will likely be mapped to some exceptions in Java, but more likely mapped to some error codes in C. # Other uses The error model and the `Status` message can be used in a variety of environments, either with or without APIs, to provide a consistent developer experience across different environments. Example uses of this error model include: - Partial errors. If a service needs to return partial errors to the client, it may embed the `Status` in the normal response to indicate the partial errors. - Workflow errors. A typical workflow has multiple steps. Each step may have a `Status` message for error reporting. - Batch operations. If a client uses batch request and batch response, the `Status` message should be used directly inside batch response, one for each error sub-response. - Asynchronous operations. If an API call embeds asynchronous operation results in its response, the status of those operations should be represented directly using the `Status` message. - Logging. If some API errors are stored in logs, the message `Status` could be used directly after any stripping needed for security/privacy reasons.

Request message for `TestIamPermissions` method.

Response message for `TestIamPermissions` method.

Request for `UnbindDeviceFromGateway`.

Response for `UnbindDeviceFromGateway`.

Details of an X.509 certificate. For informational purposes only.

Helper functions for building Tesla requests.