Cloud Pub/Sub

Welcome to the Google Cloud Pub/Sub idea forum. You can submit and vote on ideas here to tell the Pub/Sub team which features you’d like to see.

This forum is for feature suggestions. If you’re looking for help forums, look here:

We can’t wait to hear from you!

  1. Subscriber Message Filtering

    It should be possible for a subscriber to assign a "filter policy" to the topic subscription. E.g. by looking at some header attribute it should be possible to only get a subset of messages.

    337 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add Retry Count to Pub/Sub

    The way we plan to work with Pub/Sub is by pulling messages by workers. Let's say certain worker pulls the message but unable to process it. The unacknowledged message goes back to queue and will be pulled by another worker. This loop can continue indefinitely unless the 7 days limit of max message age is reached.

    It would be great to being able to set max retry count which will move the message to dead-messages-queue topic after exhausting the retry limit for the message.

    304 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  3. Better options for securing subscription push endpoints

    Better options for securing subscription push endpoints

    68 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Subscribe to topic attributes

    Subscribe to topic attributes

    42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. Provide a local emulator

    Provide a local emulator

    35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Instance Group auto-scaling based on Cloud Pub/Sub queue count

    It would be great to have an auto-scaling metric for GCE Instance Groups (or k8s 'Jobs') based on a Cloud Pub/Sub's topic count. For asynchronous workloads, as tasks are written into the topic (queue), spin up/down workers from an instance group's template. Additionaly, as Cloud Functions become fully supported, more events will are hoping to move more workloads into a dynamicly scalling into Cloud Pub/Sub - Instance Group workflow.

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  7. Remove topic limit

    10,000 topics isn't enough. I need something like 10,000 million.

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  8. 25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  9. ability to see (read/delete) messages in the console

    It would be great for testing and troubleshooting.

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  10. Provide an example of how to work with push subscriptions locally using the emulator

    When working locally I can't seem to get around the https restrictions, IMO a self signed certificate on https://localhost:port/pushendpoint should be sufficient when working locally.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  11. Configurable expiration time for topic and subscription

    Configurable expiration time for topic and subscription

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. A way to specify headers for pubsub push mechanism

    If developers have control over headers the client doesn't have to write anything to add security
    We can just use esp.
    Even though esp looks in to query parameters,
    we have to rotate the token every 24 hours for better security

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow specific metadata for notifications from Google Cloud Storage

    When GCS is registered as a publisher to a topic, we can specify *none* as the payload if all we need are the eventType, bucketId, objectId, and objectGeneration fields. This is great since the message data is only roughly 650 bytes for reasonably size bucket names and file names. For most projects, that's all we need. It's great that objectGeneration happens to be included.

    However, if we need just one other field from the object's metadata, say Content-Length for example, which would add roughly 20 more bytes, we're stuck with the entire basket of metadata fields. We'd like to specify…

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  14. 11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  15. Integration with GCS Object Change Notifications

    Integration with GCS Object Change Notifications

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Open up API for domain verification

    There is an existing set of APIs for automating the Search Console piece of getting a webhook url set up for push notifications. However, you still have to manually go into your GCP project to add the webhook to the Verified Domains under credentials in order to use it in your project. It would be great to be able to automate this piece as well, but there isn't an API we can call. Could one be created or opened up?

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  17. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  18. undelivered messages Retains period too low.

    clients cam have vacations up to 6 weeks sometimes. having 7 day retention for those messages too low.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  19. Python client library as on today is not working in an environment where http_proxy is not set

    Following error is occuring:
    ===
    E0624 07:18:51.447702419 9603 uri_parser.cc:46] bad uri.scheme: ''
    E0624 07:18:51.447727494 9603 uri_parser.cc:52] ^ here
    E0624 07:18:51.447734361 9603 http_proxy.cc:54] cannot parse value of 'http_proxy' env var

    ===
    Client Library version:

    google-cloud-pubsub 0.35.4

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defect  ·  Flag idea as inappropriate…  ·  Admin →
  20. Cloud pubsub emulator does not handle 202 response code correctly on push endpoints.

    Small discrepancy between the emulator and the production Cloud Pub/Sub.

    When responding to a push subscription with http code 202 the emulator will output the following message:

    [pubsub] INFO: Failed to push to endpoint '<endpoint here>': Fetched url '<url here>' but got a response code that is not an acknowledgement: 202

    Whereas per existing Cloud Pub/Sub documentation this should be considered a valid ack response for push endpoints:

    https://cloud.google.com/pubsub/docs/push

    (I haven't explicitely tested other response codes but I'm fairly certain that 204 and 200 are correctly handled, didn't test 201 and 102.)

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defect  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

Cloud Pub/Sub

Categories

Feedback and Knowledge Base