resource manager CAN be used with service account credentials #1426

Activity

1. elibixby

   added

   type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

   api: cloudresourcemanagerIssues related to the Resource Manager API.Issues related to the Resource Manager API.

   on Jan 29, 2016
2. elibixby

   assigned

   dhermes

   on Jan 29, 2016
3. dhermes commented on Jan 29, 2016

   

   dhermes

   on Jan 29, 2016

   Contributor

   More actions

   @elibixby Thanks for the update. When the original implementation (#1083) was done, only user accounts worked. Verifying now and then will send a PR.
4. dhermes commented on Jan 29, 2016

   

   dhermes

   on Jan 29, 2016

   Contributor

   More actions

   Confirmed. This also opens it up so that we can write system tests. Any suggestions for things that should be tested?
5. elibixby commented on Jan 29, 2016

   

   elibixby

   on Jan 29, 2016

   Author

   More actions

   Yeah. It didn't when I originally tried it either. I've been building on
   top of it and following changes, just haven't updated veneer which I should
   have contributed too ;-)

   A couple other notes:

   1. projects().get() will no longer give 404 for missing projects (in fact I
      confirmed with Elysium team that they have no plans to support any sort of
      "exists" method)
      Instead, perhaps create project should take some sort of "template" object
      that you can stick a random value in to get a valid project id?
   2. Service accounts need to be whitelisted to create projects for now.

   Stay tuned for more updates when org nodes come down the pipes.

   On Thu, Jan 28, 2016 at 6:26 PM Danny Hermes notifications@github.com
   wrote:

   Confirmed. This also opens it up so that we can write system tests. Any
   suggestions for things that should be tested?

   —
   Reply to this email directly or view it on GitHub
   #1426 (comment)
   .
6. elibixby commented on Jan 29, 2016

   

   elibixby

   on Jan 29, 2016

   Author

   More actions

   To update, projects().get() now gives 403 for all projects a user does not
   have access to. There was concern from the Elysium team of users scanning
   the entire project space, and project id is PII evidently.

   On Thu, Jan 28, 2016 at 7:38 PM Eli Bixby eli.bixby@gmail.com wrote:

   Yeah. It didn't when I originally tried it either. I've been building on
   top of it and following changes, just haven't updated veneer which I should
   have contributed too ;-)

   A couple other notes:

   1. projects().get() will no longer give 404 for missing projects (in fact
      I confirmed with Elysium team that they have no plans to support any sort
      of "exists" method)
      Instead, perhaps create project should take some sort of "template" object
      that you can stick a random value in to get a valid project id?
   2. Service accounts need to be whitelisted to create projects for now.

   Stay tuned for more updates when org nodes come down the pipes.

   On Thu, Jan 28, 2016 at 6:26 PM Danny Hermes notifications@github.com
   wrote:

   Confirmed. This also opens it up so that we can write system tests. Any
   suggestions for things that should be tested?

   —
   Reply to this email directly or view it on GitHub
   #1426 (comment)
   .
7. dhermes

   closed this as completedin #1427on Jan 29, 2016
8. theacodes

   unassigned

   dhermes

   on Sep 28, 2018
9. JustinBeckwith

   assigned

   dhermes

   on Feb 1, 2021
10. parthea

    added a commit that references this issue on Sep 22, 2023

    chore: move samples from python-docs-sample (#33)

    ...

    69c4425
11. parthea

    added a commit that references this issue on Mar 2, 2026

    chore(main): release 2.31.0 (#1426)

    ...

    0e5b903