Skip to content

GCS notification convenience methods, pubsub dependency #4097

Closed
Closed
GCS notification convenience methods, pubsub dependency#4097
Assignees
danoscarmike
Labels
api: pubsubIssues related to the Pub/Sub API.api: storageIssues related to the Cloud Storage API.type: questionRequest for information or clarification. Not an issue.

Description

@tseaver
tseaver
opened on Oct 2, 2017

In #4021, @BrandonY asked for convenience wrapprer(s) for the following:

  • Create the user-supplied topic
  • Set the appropriate IAM policy needed to support bucket notifications
  • Create a subscription to the topic

Adding this support would make storage depend on pubsub (at least optionally), and would complicate our testing story (system tests already add it). Ruby just documents what is required.

@danoscarmike, @lukesneeringer nominated you as the arbitrator for the issue.

Activity

  1. tseaver
    added
    api: pubsubIssues related to the Pub/Sub API.
    api: storageIssues related to the Cloud Storage API.
    type: questionRequest for information or clarification. Not an issue.
    on Oct 2, 2017
  2. tseaver
    assigned
    danoscarmike
    on Oct 2, 2017

  3. BrandonY commented on Oct 2, 2017

    @BrandonY
    BrandonY
    on Oct 2, 2017
    Contributor

    Without this convenience function, everyone who wants to use notifications will have to write a function that invokes around 4 calls:

    • Call GCS to request the name of the appropriate permission for your GCS bucket.
    • Call Pub/Sub to create a topic
    • Call Pub/Sub's IAM interface to add publish permission to the robot that was the response to the first RPC.
    • Call GCS to add notifications to a bucket.

    With a convenience method, the whole thing can be shortened to bucket.sendNotifications(topic).

  4. danoscarmike commented on Oct 4, 2017

    @danoscarmike
    danoscarmike
    on Oct 4, 2017
    Contributor

    Ack. @BrandonY I'll reach out to you offline.

  5. lukesneeringer commented on Oct 26, 2017

    @lukesneeringer
    lukesneeringer
    on Oct 26, 2017
    Contributor

    This was decided. We are not doing it.

  6. lukesneeringer
    closed this as completedon Oct 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

api: pubsubIssues related to the Pub/Sub API.api: storageIssues related to the Cloud Storage API.type: questionRequest for information or clarification. Not an issue.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions