Google Cloud Pub/Sub Connector

review the docid 9h7ux3mpnsmgtd5nbknd overview google cloud pub/sub integration enables an edge system to connect with google cloud pub/sub supported communication outbound (publish data from edge to google cloud pub/sub) yes inbound (subscribe to data from google cloud pub/sub to edge ) yes configurations variable detail required name enter a name for the connector yes service account key service account key is a json or p12 file containing authentication credentials for programmatic access to google services yes project id project id is a unique identifier for a specific project within the google cloud platform ecosystem yes private key private key id is a unique identifier associated with a service account's private key, used for authentication and access control in google services no client email client email is an email address associated with a service account in a google cloud project, used for authentication and access to resources no default topic the default topic for publishing yes show custom attributes if enabled, custom attributes are key value pairs that allow you to attach additional metadata to messages in a google cloud pub/sub topic for custom processing and filtering no parallel publish count parallel publish count refers to the number of concurrent message publishing operations that can be performed simultaneously using the google cloud pub/sub service, enhancing message throughput yes parallel byte threshold parallel byte threshold is the configurable limit on the size of the data payload for a batch of messages that determines when parallel publishing of messages is triggered in google cloud pub/sub for optimized data transfer no publish count threshold publish count threshold is the set limit on the number of messages in a batch that triggers publishing to google cloud pub/sub, optimizing message delivery no publish delay threshold (milliseconds) publish delay threshold (milliseconds) is the specified time interval after which accumulated messages are automatically published to google cloud pub/sub to control message delivery latency no throttling limit set a limit on the number of outbound messages per second if sending data to a server that has restrictions on the rate of incoming messages, this ensures that no messages are lost no persistent storage if enabled, messages in the outbound queue are stored on disk if there are interruptions in connection or power loss, messages will be retained and eventually sent when the connection is restored no queue mode select the sequence of data transfer fifo or lifo selecting fifo (first in first out) will send the earliest message first selecting lifo (last in first out) will send the latest message first no