Skip to content

Support autonaming of Pub/Sub Subscriptions #193

Closed
#1005
Closed
Support autonaming of Pub/Sub Subscriptions#193
#1005
Assignees
blowmage
Labels
🚨This issue needs some love.api: pubsubIssues related to the Pub/Sub API.triage meI really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Description

@blowmage
blowmage
opened on Jul 20, 2015

The Pub/Sub documentation states:

If the name is not provided in the request, the server will assign a random name for this subscription on the same project as the topic.

We are unable to make an API call to create a subscription without a name. We suspect this is an issue with the Google API Client library, since ArgumentError is being raised.

Activity

  1. blowmage
    added
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    api: pubsubIssues related to the Pub/Sub API.
    on Jul 20, 2015
  2. blowmage
    added a commit that references this issue on Jul 20, 2015

    Remove creating subscription without a name

    b80325f

  3. stephenplusplus commented on Jul 29, 2015

    @stephenplusplus
    stephenplusplus
    on Jul 29, 2015

    @tmatsuo - sorry if you've already been pinged about this elsewhere, but I couldn't find anything. Do you know if support for auto-named subscriptions is real, or if this was a documentation error?

  4. stephenplusplus commented on Aug 12, 2015

    @stephenplusplus
    stephenplusplus
    on Aug 12, 2015

    @tmatsuo friendly ping :)

  5. tmatsuo commented on May 3, 2016

    @tmatsuo
    tmatsuo
    on May 3, 2016
    Contributor

    I just found this issue! Sorry for the late reply.

    Yes, it is not currently supported on the API surface (although the internal core server supports it, thus the documentation discrepancy). Sorry about the confusion.

  6. blowmage commented on May 3, 2016

    @blowmage
    blowmage
    on May 3, 2016
    ContributorAuthor

    @tmatsuo Hah! Thanks for clarifying! We removed the docs from gcloud-ruby about this and made the name required. Glad to know the reason.

    Is this a feature that will be supported in future API versions?

  7. Draiken commented on Jun 21, 2016

    @Draiken
    Draiken
    on Jun 21, 2016

    It' been one year and I still got bitten by this issue after following the documentation here
    Is there anything I can do to help fix this issue?

  8. quartzmo
    added a commit that references this issue on Oct 31, 2016

    Fix docs for PubSub::Topic#subscribe

    7a7462c
  9. blowmage
    closed this as completedin #1005on Nov 1, 2016
  10. yoshi-automation
    added
    🚨This issue needs some love.
    triage meI really want to be triaged.
    on Apr 7, 2020
  11. JustinBeckwith
    assigned
    blowmage
    on Feb 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

🚨This issue needs some love.api: pubsubIssues related to the Pub/Sub API.triage meI really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions