\n \n topic | \n Topic name which your server subscription will belong to | \n
\n \n subscription | \n Subscription name which your server will listen to | \n
\n \n replyTopic | \n Topic name which your client subscription will belong to | \n
\n \n replySubscription | \n Subscription name which your client will listen to | \n
\n \n noAck | \n If false, manual acknowledgment mode enabled | \n
\n \n init | \n If false, topics and subscriptions will not be created, only validated | \n
\n \n checkExistence | \n If false, topics and subscriptions will not be checked, only used. This only applies when init is false | \n
\n \n useAttributes | \n Only applicable for client. If true, pattern and correlationId will be sent via message attributes. This is useful if message consumer is not NestJs microservice or you have message filtering on subscription | \n
\n \n client | \n Additional client options (read more here) | \n
\n \n publisher | \n Additional topic publisher options (read more here) | \n
\n \n subscriber | \n Additional subscriber options (read more here) | \n
\n \n scopedEnvKey | \n Scope topics and subscriptions to avoid losing messages when several people are working on the same code base. Will prefixes topics and subscriptions with this key (read more here) | \n
\n
\n\n#### Client\n\n```typescript\nconst client = new GCPubSubClient({\n client: {\n apiEndpoint: 'localhost:8681',\n projectId: 'microservice',\n },\n});\nclient\n .send('pattern', 'Hello world!')\n .subscribe((response) => console.log(response));\n```\n\n#### Context\n\nIn more sophisticated scenarios, you may want to access more information about the incoming request. When using the Pub/Sub transporter, you can access the `GCPubSubContext` object.\n\n```typescript\n@MessagePattern('notifications')\ngetNotifications(@Payload() data: number[], @Ctx() context: GCPubSubContext) {\n console.log(`Pattern: ${context.getPattern()}`);\n}\n```\n\nTo access the original Pub/Sub message (with the `attributes`, `data`, `ack` and `nack`), use the `getMessage()` method of the `GCPubSubContext` object, as follows:\n\n```typescript\n@MessagePattern('notifications')\ngetNotifications(@Payload() data: number[], @Ctx() context: GCPubSubContext) {\n console.log(context.getMessage());\n}\n```\n\n#### Message acknowledgement\n\nTo make sure a message is never lost, Pub/Sub supports [message acknowledgements](https://cloud.google.com/pubsub/docs/subscriber#at-least-once-delivery). An acknowledgement is sent back by the consumer to tell Pub/Sub that a particular message has been received, processed and that Pub/Sub is free to delete it. If a consumer dies (its subscription is closed, connection is closed, or TCP connection is lost) without sending an ack, Pub/Sub will understand that a message wasn't processed fully and will re-deliver it.\n\nTo enable manual acknowledgment mode, set the `noAck` property to `false`:\n\n```typescript\n{\n replyTopic: 'cats_topic_reply',\n replySubscription: 'cats_subscription_reply',\n noAck: false,\n client: {\n projectId: 'microservice',\n },\n},\n```\n\nWhen manual consumer acknowledgements are turned on, we must send a proper acknowledgement from the worker to signal that we are done with a task.\n\n```typescript\n@MessagePattern('notifications')\ngetNotifications(@Payload() data: number[], @Ctx() context: GCPubSubContext) {\n const originalMsg = context.getMessage();\n\n originalMsg.ack();\n}\n```\n\n#### Shutdown\n\nPub/Sub requires a graceful shutdown properly configured in order to work correctly, otherwise some messages acknowledges can be lost. Therefore, don't forget to call client close:\n\n```typescript\nexport class GCPubSubController implements OnApplicationShutdown {\n client: ClientProxy;\n\n constructor() {\n this.client = new GCPubSubClient({});\n }\n\n onApplicationShutdown() {\n return this.client.close();\n }\n}\n```\n","readmeFilename":"README.md"}![\"Nest](\"https://nestjs.com/img/logo_text.svg\"){kind=logo}