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)
// Output-based functions aren't available in Java yet
fn::invoke:
function: google-native:cloudiot/v1:getRegistry
arguments:
# arguments dictionary
The following arguments are supported:
- Location string
- Registry
Id string - Project string
- Location string
- Registry
Id string - Project string
- location String
- registry
Id String - project String
- location string
- registry
Id string - project string
- location str
- registry_
id str - project str
- location String
- registry
Id 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.
- Event
Notification 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.
- Http
Config Pulumi.Google Native. Cloud Io T. V1. Outputs. Http Config Response - The DeviceService (HTTP) configuration for this device registry.
- Log
Level 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 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
. - State
Notification 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
[]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.
- Event
Notification []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 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 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
. - 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<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.
- event
Notification 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.
- http
Config HttpConfig Response - The DeviceService (HTTP) configuration for this device registry.
- log
Level 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 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
. - 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
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.
- event
Notification 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 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 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
. - 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
Sequence[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.
- 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.
- event
Notification 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.
- http
Config Property Map - The DeviceService (HTTP) configuration for this device registry.
- log
Level 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 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
. - state
Notification 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
- Pubsub
Topic stringName - A Cloud Pub/Sub topic name. For example,
projects/myProject/topics/deviceEvents
. - Subfolder
Matches 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 stringName - A Cloud Pub/Sub topic name. For example,
projects/myProject/topics/deviceEvents
. - Subfolder
Matches 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 StringName - A Cloud Pub/Sub topic name. For example,
projects/myProject/topics/deviceEvents
. - subfolder
Matches 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 stringName - A Cloud Pub/Sub topic name. For example,
projects/myProject/topics/deviceEvents
. - subfolder
Matches 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.
- pubsub
Topic StringName - A Cloud Pub/Sub topic name. For example,
projects/myProject/topics/deviceEvents
. - subfolder
Matches 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
- Http
Enabled stringState - If enabled, allows devices to use DeviceService via the HTTP protocol. Otherwise, any requests to DeviceService will fail for this registry.
- Http
Enabled stringState - If enabled, allows devices to use DeviceService via the HTTP protocol. Otherwise, any requests to DeviceService will fail for this registry.
- http
Enabled StringState - If enabled, allows devices to use DeviceService via the HTTP protocol. Otherwise, any requests to DeviceService will fail for this registry.
- http
Enabled 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.
- http
Enabled StringState - If enabled, allows devices to use DeviceService via the HTTP protocol. Otherwise, any requests to DeviceService will fail for this registry.
MqttConfigResponse
- Mqtt
Enabled stringState - If enabled, allows connections using the MQTT protocol. Otherwise, MQTT connections to this registry will fail.
- Mqtt
Enabled stringState - If enabled, allows connections using the MQTT protocol. Otherwise, MQTT connections to this registry will fail.
- mqtt
Enabled StringState - If enabled, allows connections using the MQTT protocol. Otherwise, MQTT connections to this registry will fail.
- mqtt
Enabled 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.
- mqtt
Enabled 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
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
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
X509Certificate
Details 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
- Public
Key Pulumi.Certificate Google Native. Cloud Io T. V1. Inputs. Public 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.
- public
Key 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.
- public_
key_ Publiccertificate Key Certificate Response - A public key certificate used to verify the device credentials.
- public
Key Property MapCertificate - A public key certificate used to verify the device credentials.
StateNotificationConfigResponse
- Pubsub
Topic stringName - A Cloud Pub/Sub topic name. For example,
projects/myProject/topics/deviceEvents
.
- Pubsub
Topic stringName - A Cloud Pub/Sub topic name. For example,
projects/myProject/topics/deviceEvents
.
- pubsub
Topic StringName - A Cloud Pub/Sub topic name. For example,
projects/myProject/topics/deviceEvents
.
- pubsub
Topic 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
.
- pubsub
Topic StringName - A Cloud Pub/Sub topic name. For example,
projects/myProject/topics/deviceEvents
.
X509CertificateDetailsResponse
- Expiry
Time string - The time the certificate becomes invalid.
- Issuer string
- The entity that signed the certificate.
- Public
Key stringType - The type of public key in the certificate.
- Signature
Algorithm string - The algorithm used to sign the certificate.
- Start
Time string - The time the certificate becomes valid.
- Subject string
- The entity the certificate and public key belong to.
- Expiry
Time string - The time the certificate becomes invalid.
- Issuer string
- The entity that signed the certificate.
- Public
Key stringType - The type of public key in the certificate.
- Signature
Algorithm string - The algorithm used to sign the certificate.
- Start
Time string - The time the certificate becomes valid.
- Subject string
- The entity the certificate and public key belong to.
- expiry
Time String - The time the certificate becomes invalid.
- issuer String
- The entity that signed the certificate.
- public
Key StringType - The type of public key in the certificate.
- signature
Algorithm String - The algorithm used to sign the certificate.
- start
Time String - The time the certificate becomes valid.
- subject String
- The entity the certificate and public key belong to.
- expiry
Time string - The time the certificate becomes invalid.
- issuer string
- The entity that signed the certificate.
- public
Key stringType - The type of public key in the certificate.
- signature
Algorithm string - The algorithm used to sign the certificate.
- start
Time 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.
- expiry
Time String - The time the certificate becomes invalid.
- issuer String
- The entity that signed the certificate.
- public
Key StringType - The type of public key in the certificate.
- signature
Algorithm String - The algorithm used to sign the certificate.
- start
Time 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