Struct google_cloudiot1::DeviceRegistry

pub struct DeviceRegistry {
    pub name: Option<String>,
    pub state_notification_config: Option<StateNotificationConfig>,
    pub log_level: Option<String>,
    pub mqtt_config: Option<MqttConfig>,
    pub http_config: Option<HttpConfig>,
    pub event_notification_configs: Option<Vec<EventNotificationConfig>>,
    pub credentials: Option<Vec<RegistryCredential>>,
    pub id: Option<String>,
}

A container for a group of devices.

Activities

This type is used in activities, which are methods you may call on this type or where this type is involved in. The list links the activity name, along with information about where it is used (one of request and response).

• locations registries patch projects (request|response)
• locations registries create projects (request|response)
• locations registries get projects (response)

Fields

name: Option<String>

The resource path name. For example, projects/example-project/locations/us-central1/registries/my-registry.

state_notification_config: Option<StateNotificationConfig>

The configuration for notification of new states received from the device. State updates are guaranteed to be stored in the state history, but notifications to Cloud Pub/Sub are not guaranteed. For example, if permissions are misconfigured or the specified topic doesn't exist, no notification will be published but the state will still be stored in Cloud IoT Core.

log_level: Option<String>

Beta Feature

The default logging verbosity for activity from devices in this registry. The verbosity level can be overridden by Device.log_level.

mqtt_config: Option<MqttConfig>

The MQTT configuration for this device registry.

http_config: Option<HttpConfig>

The DeviceService (HTTP) configuration for this device registry.

event_notification_configs: Option<Vec<EventNotificationConfig>>

The configuration for notification of telemetry events received from the device. All telemetry events that were successfully published by the device and acknowledged by Cloud IoT Core are guaranteed to be delivered to Cloud Pub/Sub. If multiple configurations match a message, only the first matching configuration is used. If you try to publish a device telemetry event using MQTT without specifying a Cloud Pub/Sub topic for the device's registry, the connection closes automatically. If you try to do so using an HTTP connection, an error is returned. Up to 10 configurations may be provided.

credentials: Option<Vec<RegistryCredential>>

The credentials used to verify the device credentials. No more than 10 credentials can be bound to a single registry at a time. The verification process occurs at the time of device creation or update. If this field is empty, no verification is performed. Otherwise, the credentials of a newly created device or added credentials of an updated device should be signed with one of these registry credentials.

Note, however, that existing devices will never be affected by modifications to this list of credentials: after a device has been successfully created in a registry, it should be able to connect even if its registry credentials are revoked, deleted, or modified.

id: Option<String>

The identifier of this device registry. For example, myRegistry.

Trait Implementations

impl Default for DeviceRegistry

fn default() -> DeviceRegistry

Returns the "default value" for a type.

impl Clone for DeviceRegistry

fn clone(&self) -> DeviceRegistry

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for DeviceRegistry

fn fmt(&self, f: &mut Formatter) -> Result

Formats the value using the given formatter.

impl RequestValue for DeviceRegistry

impl ResponseResult for DeviceRegistry