Skip to content

Storage: Implement Bucket-Level IAM Policy Management #2057

Description

@stephenplusplus

Activity

  1. added
    priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.
    and removed
    priority: p0Highest priority. Critical issue. P0 implies highest priority.
    on Mar 20, 2017
  2. bjwatson commented on Mar 20, 2017

    @bjwatson

    This is not release blocking. The API team has pushed out bucket-level IAM until later.

  3. stephenplusplus commented on Mar 24, 2017

    @stephenplusplus
    ContributorAuthor

    Marking as blocked as we're still waiting on whitelisting.

  4. lukesneeringer commented on Mar 24, 2017

    @lukesneeringer
    Contributor

    Summoning @elibixby. Not sure if you are the right person, but I think you might be -- can we get whitelisted, pretty please? :-)

  5. elibixby commented on Mar 24, 2017

    @elibixby

    Nope unfortunately, try pinging yarbrough@ ... You might also want to get notified whitelisted for the new GCS Change Notifications (which work via Pub/Sub) while you're at it.

  6. stephenplusplus commented on Mar 27, 2017

    @stephenplusplus
    ContributorAuthor

    Un-blocked-- my account and the system tests account seems to have been whitelisted.

    Stuck on another issue, though if anyone can help #2060 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

api: storageIssues related to the Cloud Storage API.priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions