@arcane-utils/pubsub

CHANGE LOG

V 1.6.0

Re-apply the Avro monitoring path on top of 1.5.0: publishProductFlowMonitoringMessage now publishes to an Avro topic (adds a required projectId param and a logs_explorer_url in additional_info), and publishAvroRecords caches the topic metadata and Avro schema per process to avoid hitting the Pub/Sub admin API quota on every publish. Re-exports the gcp_component_retrieve_info helpers.

V 1.5.0

publishStorageMessage handles additional metadata (Record<string, string | string[]>) to be added to the message metadata

V 1.4.1

⚠️ UNSAFE — do not use. Built on reverted monitoring/Avro-caching changes. publishStorageMessage handle additional metadata to be added to the message metadata

V 1.4.0

⚠️ UNSAFE — do not use. Built on reverted monitoring/Avro-caching changes. Cache topic metadata and Avro schema in publishAvroRecords to avoid hitting the Pub/Sub admin API quota on every publish

V 1.3.2

⚠️ UNSAFE — do not use. Built on reverted monitoring/Avro-caching changes. Fix long timestamp in publishProductFlowMonitoringMessage

V 1.3.0

⚠️ UNSAFE — do not use. Built on reverted monitoring/Avro-caching changes. Publish monitoring pf message with avro schema

V 1.2.5

Use commonjs module

V 1.2.3

Expose publishAvroRecords

V 1.2.2

Fix function publish validate with a schema

V 1.2.1

Fix function publish validate with a schema

V 1.2.0

Add a function publish validate with a schema

V 1.1.12

Finally make package functional after many tries

V 1.0.1

Expose google package lib.

V 1.0.0

Init component.