Request forBindDeviceToGateway.

Response forBindDeviceToGateway.

Request forCreateDeviceRegistry.

Request forCreateDevice.

Request forDeleteDeviceRegistry.

Request forDeleteDevice.

The device resource.

The device configuration. Eventually delivered to devices.

A server-stored device credential used for authentication.

.. _oneof:https://proto-plus-python.readthedocs.io/en/stable/fields.html#oneofs-mutually-exclusive-fields

A container for a group of devices.

The device state, as reported by the device.

The configuration for forwarding telemetry events.

The gateway authorization/authentication method. This settingdetermines how Cloud IoT Core authorizes/authenticate devices toaccess the gateway.

Values: GATEWAY_AUTH_METHOD_UNSPECIFIED (0): No authentication/authorization method specified. No devices are allowed to access the gateway. ASSOCIATION_ONLY (1): The device is authenticated through the gateway association only. Device credentials are ignored even if provided. DEVICE_AUTH_TOKEN_ONLY (2): The device is authenticated through its own credentials. Gateway association is not checked. ASSOCIATION_AND_DEVICE_AUTH_TOKEN (3): The device is authenticated through both device credentials and gateway association. The device must be bound to the gateway and must provide its own credentials.

Gateway-related configuration and state.

Options for limiting the list based on gateway type andassociations.

This message hasoneof_ fields (mutually exclusive fields).For each oneof, at most one member field can be set at the same time.Setting any member of the oneof automatically clears all othermembers.

.. _oneof:https://proto-plus-python.readthedocs.io/en/stable/fields.html#oneofs-mutually-exclusive-fields

Gateway type.

Values: GATEWAY_TYPE_UNSPECIFIED (0): If unspecified, the device is considered a non-gateway device. GATEWAY (1): The device is a gateway. NON_GATEWAY (2): The device is not a gateway.

Request forGetDeviceRegistry.

Request forGetDevice.

The configuration of the HTTP bridge for a device registry.

Indicates whether DeviceService (HTTP) is enabled or disabledfor the registry. See the field description for details.

Values: HTTP_STATE_UNSPECIFIED (0): No HTTP state specified. If not specified, DeviceService will be enabled by default. HTTP_ENABLED (1): Enables DeviceService (HTTP) service for the registry. HTTP_DISABLED (2): Disables DeviceService (HTTP) service for the registry.

Request forListDeviceConfigVersions.

Response forListDeviceConfigVersions.

Request forListDeviceRegistries.

Response forListDeviceRegistries.

Request forListDeviceStates.

Response forListDeviceStates.

Request forListDevices.

Response forListDevices.

Beta Feature

The logging verbosity for device activity. Specifies which eventsshould be written to logs. For example, if the LogLevel is ERROR,only events that terminate in errors will be logged. LogLevel isinclusive; enabling INFO logging will also enable ERROR logging.

Values: LOG_LEVEL_UNSPECIFIED (0): No logging specified. If not specified, logging will be disabled. NONE (10): Disables logging. ERROR (20): Error events will be logged. INFO (30): Informational events will be logged, such as connections and disconnections. DEBUG (40): All events will be logged.

Request forModifyCloudToDeviceConfig.

The configuration of MQTT for a device registry.

Indicates whether an MQTT connection is enabled or disabled.See the field description for details.

Values: MQTT_STATE_UNSPECIFIED (0): No MQTT state specified. If not specified, MQTT will be enabled by default. MQTT_ENABLED (1): Enables a MQTT connection. MQTT_DISABLED (2): Disables a MQTT connection.

A public key certificate format and data.

The supported formats for the public key.

Values: UNSPECIFIED_PUBLIC_KEY_CERTIFICATE_FORMAT (0): The format has not been specified. This is an invalid default value and must not be used. X509_CERTIFICATE_PEM (1): An X.509v3 certificate (RFC5280 <https://www.ietf.org/rfc/rfc5280.txt>__), encoded in base64, and wrapped by-----BEGIN CERTIFICATE----- and-----END CERTIFICATE-----.

A public key format and data.

The supported formats for the public key.

Values: UNSPECIFIED_PUBLIC_KEY_FORMAT (0): The format has not been specified. This is an invalid default value and must not be used. RSA_PEM (3): An RSA public key encoded in base64, and wrapped by-----BEGIN PUBLIC KEY----- and-----END PUBLIC KEY-----. This can be used to verifyRS256 signatures in JWT tokens (RFC7518 <https://www.ietf.org/rfc/rfc7518.txt>). RSA_X509_PEM (1): As RSA_PEM, but wrapped in an X.509v3 certificate (RFC5280 <https://www.ietf.org/rfc/rfc5280.txt>), encoded in base64, and wrapped by-----BEGIN CERTIFICATE----- and-----END CERTIFICATE-----. ES256_PEM (2): Public key for the ECDSA algorithm using P-256 and SHA-256, encoded in base64, and wrapped by-----BEGIN PUBLIC KEY----- and-----END PUBLIC KEY-----. This can be used to verify JWT tokens with theES256 algorithm (RFC7518 <https://www.ietf.org/rfc/rfc7518.txt>). This curve is defined inOpenSSL <https://www.openssl.org/> as theprime256v1 curve. ES256_X509_PEM (4): As ES256_PEM, but wrapped in an X.509v3 certificate (RFC5280 <https://www.ietf.org/rfc/rfc5280.txt>__), encoded in base64, and wrapped by-----BEGIN CERTIFICATE----- and-----END CERTIFICATE-----.

A server-stored registry credential used to validate devicecredentials.

.. _oneof:https://proto-plus-python.readthedocs.io/en/stable/fields.html#oneofs-mutually-exclusive-fields

Request forSendCommandToDevice.

Response forSendCommandToDevice.

The configuration for notification of new states receivedfrom the device.

Request forUnbindDeviceFromGateway.

Response forUnbindDeviceFromGateway.

Request forUpdateDeviceRegistry.

Request forUpdateDevice.

Details of an X.509 certificate. For informational purposesonly.