Basic Operations


The following basic operations are available for the Google Cloud Injector Module and can be executed within any of the available Ignition scopes using the format system.cirruslink.google.operation



where:







Configuration changes made through scripting do have the same validation as when made through the UI. 

For example, attempting to delete a Sets configuring that is being referenced by a Servers configuration will result in no action being performed.





Google Cloud Injector 'type' keys



Google Cloud Injector 'general' keys


enabledboolean

Whether or not the configuration resource is enabled


Google Cloud Injector 'iot-core' keys


enabledboolean

Whether or not the configuration resource is enabled

namestring

The unique name for the configuration resource

mqttEndpointUrlstringThe MQTT Server Endpoint
projectIdstringThe GCP project under which this device is provisioned
cloudRegionstringThe GCP cloud region under which this device is provisioned
registryIdstringThe GCP registry ID under which this device is provisioned
deviceIdstringThe GCP ID of this device
privateKeyFileContentsstringThe file contents of the private key
algorithmstringThe algorithm type used by the key file
serverSetstringThe Set this Event Hub connection is associated with
proxyTypestringThe Proxy Type if a proxy server is being used
proxyHostnamestringThe Proxy hostname if a proxy server is being used
proxyPortintegerThe Proxy port number if a proxy server is being used
keepAliveintegerThe MQTT Client keep alive time (in seconds)
historyEnabledbooleanEnable Store and Forward capabilities for this stream
historyStoreTypestringThe Type of this Store & Forward mechanism
partionPeriodstringThe partitioning scheme to use for the Disk-backed history store (e.g. HOUR, MINUTE, DAY, etc)
historyMaxSizeintegerMaximum number of megabytes history can use before dropping the data
trimmerTaskPeriodMultiplierintegerA integer multiplier which is applied to the 'storageMonitorPeriod' which results in the period in which to trim potential excess history
historyMaxAgeintegerMaximum number of minutes to store history before dropping the data
queryTimeoutintegerThe H2 DB query timeout in seconds for the disk-backed history store
maxSizeintegerMaximum message size before dividing into multiple messages
maxThroughputlongMaximum throughput per second in bytes. The module will throttle messages to prevent exceeding this max limit
expirationintegerThe number of minutes before the session token expires
tokenAutoRefreshEnabledbooleanSession Token Auto-refresh
h2dbDirectorystringDirectory to store the H2 Database in. Applicable for Disk-backed history store only
h2dbPortintegerTCP Port to connect to H2 Database. Applicable for Disk-backed history store only
dbMaxMessageSizeintegerThe Max Message size allowed in the Store and Forward DB. This only applies to Disk-Backed history stores
republishBirthsbooleanWhether or not to republish BIRTH messages on reestablishing connection to the endpoint



Google Cloud Injector 'server-set' keys


enabledboolean

Whether or not the configuration resource is enabled

namestring

The unique name for the configuration resource

descriptionstringDescription of this Set
pushPolicystringThe Push Policy defines whether all cloud end-points in a set will be pushed to or only one will at a time - PUSH_TO_ALL or PUSH_TO_ANY


Google Cloud Injector 'agent' keys


enabledboolean

Whether or not the configuration resource is enabled

namestring

The unique name for the configuration resource

tagProviderstringThe Name of the tag provider
tagPathstringA path to the root folder where the tag tree starts (optional)
pushTriggerstring

The trigger to use when pushing data - EVENT_DRIVEN, PERIODIC or HYBRID

tagPacingPeriodlong

If using an EVENT_DRIVEN Push trigger, the waiting period in milliseconds after an initial tag change event before pushing all changed tags.

If using PERIODIC, the number of milliseconds to wait between pushing all data

convertUdtsbooleanConverts UDT members to normal Tags
sendAllPropsbooleanSend all properties, including non-default properties, in Sparkplug BIRTH messages
includeQualityContextbooleanInclude the metric 'quality context' string in addition to the quality codes for metrics
includeInfoFoldersbooleanPush all Node and Device Info and Control folder information (from MQTT Engine) rather than excluding it
publishUdtDefinitionsbooleanPublish UDT Definitions in BIRTH
optimizeUdtsbooleanOptimizes UDT payload sizes in NDATA and DDATA payloads
serverSetstringThe Set this Agent is associated with
groupIdstringAn ID representing a logical grouping of Edge Nodes and Devices (optional)
edgeNodeIdstringAn ID representing an Edge or Network (EoN) Node (optional)
deviceIdstringAn ID representing a Device (optional)
filteredPropertiesstringA semicolon delimited list of Tag properties to filter/block from being published
birthSettleDelaylongThe amount of time to wait after setting the BIRTH timestamp before fetching the cached BIRTH payloads