Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi
google-native.cloudiot/v1.getRegistry
Explore with Pulumi AI
Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi
Gets a device registry configuration.
Using getRegistry
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getRegistry(args: GetRegistryArgs, opts?: InvokeOptions): Promise<GetRegistryResult>
function getRegistryOutput(args: GetRegistryOutputArgs, opts?: InvokeOptions): Output<GetRegistryResult>def get_registry(location: Optional[str] = None,
                 project: Optional[str] = None,
                 registry_id: Optional[str] = None,
                 opts: Optional[InvokeOptions] = None) -> GetRegistryResult
def get_registry_output(location: Optional[pulumi.Input[str]] = None,
                 project: Optional[pulumi.Input[str]] = None,
                 registry_id: Optional[pulumi.Input[str]] = None,
                 opts: Optional[InvokeOptions] = None) -> Output[GetRegistryResult]func LookupRegistry(ctx *Context, args *LookupRegistryArgs, opts ...InvokeOption) (*LookupRegistryResult, error)
func LookupRegistryOutput(ctx *Context, args *LookupRegistryOutputArgs, opts ...InvokeOption) LookupRegistryResultOutput> Note: This function is named LookupRegistry in the Go SDK.
public static class GetRegistry 
{
    public static Task<GetRegistryResult> InvokeAsync(GetRegistryArgs args, InvokeOptions? opts = null)
    public static Output<GetRegistryResult> Invoke(GetRegistryInvokeArgs args, InvokeOptions? opts = null)
}public static CompletableFuture<GetRegistryResult> getRegistry(GetRegistryArgs args, InvokeOptions options)
public static Output<GetRegistryResult> getRegistry(GetRegistryArgs args, InvokeOptions options)
fn::invoke:
  function: google-native:cloudiot/v1:getRegistry
  arguments:
    # arguments dictionaryThe following arguments are supported:
- Location string
- RegistryId string
- Project string
- Location string
- RegistryId string
- Project string
- location String
- registryId String
- project String
- location string
- registryId string
- project string
- location str
- registry_id str
- project str
- location String
- registryId String
- project String
getRegistry Result
The following output properties are available:
- Credentials
List<Pulumi.Google Native. Cloud Io T. V1. Outputs. Registry Credential Response> 
- 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.
- EventNotification List<Pulumi.Configs Google Native. Cloud Io T. V1. Outputs. Event Notification Config Response> 
- 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.
- HttpConfig Pulumi.Google Native. Cloud Io T. V1. Outputs. Http Config Response 
- The DeviceService (HTTP) configuration for this device registry.
- LogLevel string
- Beta Feature The default logging verbosity for activity from devices in this registry. The verbosity level can be overridden by Device.log_level.
- MqttConfig Pulumi.Google Native. Cloud Io T. V1. Outputs. Mqtt Config Response 
- The MQTT configuration for this device registry.
- Name string
- The resource path name. For example, projects/example-project/locations/us-central1/registries/my-registry.
- StateNotification Pulumi.Config Google Native. Cloud Io T. V1. Outputs. State Notification Config Response 
- 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.
- Credentials
[]RegistryCredential Response 
- 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.
- EventNotification []EventConfigs Notification Config Response 
- 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.
- HttpConfig HttpConfig Response 
- The DeviceService (HTTP) configuration for this device registry.
- LogLevel string
- Beta Feature The default logging verbosity for activity from devices in this registry. The verbosity level can be overridden by Device.log_level.
- MqttConfig MqttConfig Response 
- The MQTT configuration for this device registry.
- Name string
- The resource path name. For example, projects/example-project/locations/us-central1/registries/my-registry.
- StateNotification StateConfig Notification Config Response 
- 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.
- credentials
List<RegistryCredential Response> 
- 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.
- eventNotification List<EventConfigs Notification Config Response> 
- 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.
- httpConfig HttpConfig Response 
- The DeviceService (HTTP) configuration for this device registry.
- logLevel String
- Beta Feature The default logging verbosity for activity from devices in this registry. The verbosity level can be overridden by Device.log_level.
- mqttConfig MqttConfig Response 
- The MQTT configuration for this device registry.
- name String
- The resource path name. For example, projects/example-project/locations/us-central1/registries/my-registry.
- stateNotification StateConfig Notification Config Response 
- 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.
- credentials
RegistryCredential Response[] 
- 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.
- eventNotification EventConfigs Notification Config Response[] 
- 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.
- httpConfig HttpConfig Response 
- The DeviceService (HTTP) configuration for this device registry.
- logLevel string
- Beta Feature The default logging verbosity for activity from devices in this registry. The verbosity level can be overridden by Device.log_level.
- mqttConfig MqttConfig Response 
- The MQTT configuration for this device registry.
- name string
- The resource path name. For example, projects/example-project/locations/us-central1/registries/my-registry.
- stateNotification StateConfig Notification Config Response 
- 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.
- credentials
Sequence[RegistryCredential Response] 
- 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.
- event_notification_ Sequence[Eventconfigs Notification Config Response] 
- 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.
- http_config HttpConfig Response 
- The DeviceService (HTTP) configuration for this device registry.
- log_level str
- 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 MqttConfig Response 
- The MQTT configuration for this device registry.
- name str
- The resource path name. For example, projects/example-project/locations/us-central1/registries/my-registry.
- state_notification_ Stateconfig Notification Config Response 
- 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.
- credentials List<Property Map>
- 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.
- eventNotification List<Property Map>Configs 
- 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.
- httpConfig Property Map
- The DeviceService (HTTP) configuration for this device registry.
- logLevel String
- Beta Feature The default logging verbosity for activity from devices in this registry. The verbosity level can be overridden by Device.log_level.
- mqttConfig Property Map
- The MQTT configuration for this device registry.
- name String
- The resource path name. For example, projects/example-project/locations/us-central1/registries/my-registry.
- stateNotification Property MapConfig 
- 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.
Supporting Types
EventNotificationConfigResponse   
- PubsubTopic stringName 
- A Cloud Pub/Sub topic name. For example, projects/myProject/topics/deviceEvents.
- SubfolderMatches string
- If the subfolder name matches this string exactly, this configuration will be used. The string must not include the leading '/' character. If empty, all strings are matched. This field is used only for telemetry events; subfolders are not supported for state changes.
- PubsubTopic stringName 
- A Cloud Pub/Sub topic name. For example, projects/myProject/topics/deviceEvents.
- SubfolderMatches string
- If the subfolder name matches this string exactly, this configuration will be used. The string must not include the leading '/' character. If empty, all strings are matched. This field is used only for telemetry events; subfolders are not supported for state changes.
- pubsubTopic StringName 
- A Cloud Pub/Sub topic name. For example, projects/myProject/topics/deviceEvents.
- subfolderMatches String
- If the subfolder name matches this string exactly, this configuration will be used. The string must not include the leading '/' character. If empty, all strings are matched. This field is used only for telemetry events; subfolders are not supported for state changes.
- pubsubTopic stringName 
- A Cloud Pub/Sub topic name. For example, projects/myProject/topics/deviceEvents.
- subfolderMatches string
- If the subfolder name matches this string exactly, this configuration will be used. The string must not include the leading '/' character. If empty, all strings are matched. This field is used only for telemetry events; subfolders are not supported for state changes.
- pubsub_topic_ strname 
- A Cloud Pub/Sub topic name. For example, projects/myProject/topics/deviceEvents.
- subfolder_matches str
- If the subfolder name matches this string exactly, this configuration will be used. The string must not include the leading '/' character. If empty, all strings are matched. This field is used only for telemetry events; subfolders are not supported for state changes.
- pubsubTopic StringName 
- A Cloud Pub/Sub topic name. For example, projects/myProject/topics/deviceEvents.
- subfolderMatches String
- If the subfolder name matches this string exactly, this configuration will be used. The string must not include the leading '/' character. If empty, all strings are matched. This field is used only for telemetry events; subfolders are not supported for state changes.
HttpConfigResponse  
- HttpEnabled stringState 
- If enabled, allows devices to use DeviceService via the HTTP protocol. Otherwise, any requests to DeviceService will fail for this registry.
- HttpEnabled stringState 
- If enabled, allows devices to use DeviceService via the HTTP protocol. Otherwise, any requests to DeviceService will fail for this registry.
- httpEnabled StringState 
- If enabled, allows devices to use DeviceService via the HTTP protocol. Otherwise, any requests to DeviceService will fail for this registry.
- httpEnabled stringState 
- If enabled, allows devices to use DeviceService via the HTTP protocol. Otherwise, any requests to DeviceService will fail for this registry.
- http_enabled_ strstate 
- If enabled, allows devices to use DeviceService via the HTTP protocol. Otherwise, any requests to DeviceService will fail for this registry.
- httpEnabled StringState 
- If enabled, allows devices to use DeviceService via the HTTP protocol. Otherwise, any requests to DeviceService will fail for this registry.
MqttConfigResponse  
- MqttEnabled stringState 
- If enabled, allows connections using the MQTT protocol. Otherwise, MQTT connections to this registry will fail.
- MqttEnabled stringState 
- If enabled, allows connections using the MQTT protocol. Otherwise, MQTT connections to this registry will fail.
- mqttEnabled StringState 
- If enabled, allows connections using the MQTT protocol. Otherwise, MQTT connections to this registry will fail.
- mqttEnabled stringState 
- If enabled, allows connections using the MQTT protocol. Otherwise, MQTT connections to this registry will fail.
- mqtt_enabled_ strstate 
- If enabled, allows connections using the MQTT protocol. Otherwise, MQTT connections to this registry will fail.
- mqttEnabled StringState 
- If enabled, allows connections using the MQTT protocol. Otherwise, MQTT connections to this registry will fail.
PublicKeyCertificateResponse   
- Certificate string
- The certificate data.
- Format string
- The certificate format.
- X509Details
Pulumi.Google Native. Cloud Io T. V1. Inputs. X509Certificate Details Response 
- [Output only] The certificate details. Used only for X.509 certificates.
- Certificate string
- The certificate data.
- Format string
- The certificate format.
- X509Details
X509CertificateDetails Response 
- [Output only] The certificate details. Used only for X.509 certificates.
- certificate String
- The certificate data.
- format String
- The certificate format.
- x509Details
X509CertificateDetails Response 
- [Output only] The certificate details. Used only for X.509 certificates.
- certificate string
- The certificate data.
- format string
- The certificate format.
- x509Details
X509CertificateDetails Response 
- [Output only] The certificate details. Used only for X.509 certificates.
- certificate str
- The certificate data.
- format str
- The certificate format.
- x509_details X509CertificateDetails Response 
- [Output only] The certificate details. Used only for X.509 certificates.
- certificate String
- The certificate data.
- format String
- The certificate format.
- x509Details Property Map
- [Output only] The certificate details. Used only for X.509 certificates.
RegistryCredentialResponse  
- PublicKey Pulumi.Certificate Google Native. Cloud Io T. V1. Inputs. Public Key Certificate Response 
- A public key certificate used to verify the device credentials.
- PublicKey PublicCertificate Key Certificate Response 
- A public key certificate used to verify the device credentials.
- publicKey PublicCertificate Key Certificate Response 
- A public key certificate used to verify the device credentials.
- publicKey PublicCertificate Key Certificate Response 
- A public key certificate used to verify the device credentials.
- public_key_ Publiccertificate Key Certificate Response 
- A public key certificate used to verify the device credentials.
- publicKey Property MapCertificate 
- A public key certificate used to verify the device credentials.
StateNotificationConfigResponse   
- PubsubTopic stringName 
- A Cloud Pub/Sub topic name. For example, projects/myProject/topics/deviceEvents.
- PubsubTopic stringName 
- A Cloud Pub/Sub topic name. For example, projects/myProject/topics/deviceEvents.
- pubsubTopic StringName 
- A Cloud Pub/Sub topic name. For example, projects/myProject/topics/deviceEvents.
- pubsubTopic stringName 
- A Cloud Pub/Sub topic name. For example, projects/myProject/topics/deviceEvents.
- pubsub_topic_ strname 
- A Cloud Pub/Sub topic name. For example, projects/myProject/topics/deviceEvents.
- pubsubTopic StringName 
- A Cloud Pub/Sub topic name. For example, projects/myProject/topics/deviceEvents.
X509CertificateDetailsResponse  
- ExpiryTime string
- The time the certificate becomes invalid.
- Issuer string
- The entity that signed the certificate.
- PublicKey stringType 
- The type of public key in the certificate.
- SignatureAlgorithm string
- The algorithm used to sign the certificate.
- StartTime string
- The time the certificate becomes valid.
- Subject string
- The entity the certificate and public key belong to.
- ExpiryTime string
- The time the certificate becomes invalid.
- Issuer string
- The entity that signed the certificate.
- PublicKey stringType 
- The type of public key in the certificate.
- SignatureAlgorithm string
- The algorithm used to sign the certificate.
- StartTime string
- The time the certificate becomes valid.
- Subject string
- The entity the certificate and public key belong to.
- expiryTime String
- The time the certificate becomes invalid.
- issuer String
- The entity that signed the certificate.
- publicKey StringType 
- The type of public key in the certificate.
- signatureAlgorithm String
- The algorithm used to sign the certificate.
- startTime String
- The time the certificate becomes valid.
- subject String
- The entity the certificate and public key belong to.
- expiryTime string
- The time the certificate becomes invalid.
- issuer string
- The entity that signed the certificate.
- publicKey stringType 
- The type of public key in the certificate.
- signatureAlgorithm string
- The algorithm used to sign the certificate.
- startTime string
- The time the certificate becomes valid.
- subject string
- The entity the certificate and public key belong to.
- expiry_time str
- The time the certificate becomes invalid.
- issuer str
- The entity that signed the certificate.
- public_key_ strtype 
- The type of public key in the certificate.
- signature_algorithm str
- The algorithm used to sign the certificate.
- start_time str
- The time the certificate becomes valid.
- subject str
- The entity the certificate and public key belong to.
- expiryTime String
- The time the certificate becomes invalid.
- issuer String
- The entity that signed the certificate.
- publicKey StringType 
- The type of public key in the certificate.
- signatureAlgorithm String
- The algorithm used to sign the certificate.
- startTime String
- The time the certificate becomes valid.
- subject String
- The entity the certificate and public key belong to.
Package Details
- Repository
- Google Cloud Native pulumi/pulumi-google-native
- License
- Apache-2.0
Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi