components-contrib
components-contrib copied to clipboard
dapr
Require GCP PUBSUB component to support publish or consumer message with custom attributes
Describe the feature
The current GCP PUB/SUB DAPR component does not support publishing or consuming messages with custom attributes. This can be a limitation for applications that need to track additional information about messages, such as the order in which they were received, the source of the message, or the status of the message processing.
I propose that the GCP PUB/SUB DAPR component be updated to support publishing or consuming messages with custom attributes. This would allow applications to track additional information about messages, which could improve the overall observability and manageability of their applications. The similar feature has been implemented by azure service bus topic pubsub component
Benefits:
Improved observability and manageability of applications Increased flexibility for applications to track additional information about messages Reduced complexity of applications by eliminating the need to implement custom message-handling logic Use cases:
Tracking the order in which messages were received Tracking the source of messages Tracking the status of message processing Implementing custom message filtering Implementing custom message routing
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.