Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System tests for resource manager #1105

Closed
dhermes opened this issue Aug 27, 2015 · 5 comments
Closed

System tests for resource manager #1105

dhermes opened this issue Aug 27, 2015 · 5 comments
Assignees
Labels
api: cloudresourcemanager Issues related to the Resource Manager API. priority: p2 Moderately-important priority. Fix may not be included in next release. testing

Comments

@dhermes
Copy link
Contributor

dhermes commented Aug 27, 2015

After #1083, we now need system tests for the Resource Manager API.

Since the API requires using a user account (not a service account), this is a bit hairy.

For oauth2client's system tests, we ended up just using a simple refresh token for my personal GMail account. The token is only authorized with the email scope, so it's not a very big deal, but for this one, it may be a bigger deal?

@dhermes dhermes added testing api: cloudresourcemanager Issues related to the Resource Manager API. labels Aug 27, 2015
@jgeewax
Copy link
Contributor

jgeewax commented Aug 27, 2015

Later this yea, I hear that service accounts will be able to own (and therefore create) projects -- and then this problem goes away.

In the meantime, we could always make the choice to punt on this and just "not have system tests for RM" ...? I suspect this isn't going to be a frequently used API...

@dhermes
Copy link
Contributor Author

dhermes commented Aug 27, 2015

OK.

@dhermes
Copy link
Contributor Author

dhermes commented Dec 31, 2015

@jgeewax Any kind of update on this?

@tseaver
Copy link
Contributor

tseaver commented Mar 16, 2016

Apparently #1614 is due to a similar policy (sinks can only be created by user accounts). @jgeewax can you lean on the teams responsible to fix that issue?

@lukesneeringer lukesneeringer added the priority: p2 Moderately-important priority. Fix may not be included in next release. label Apr 19, 2017
@lukesneeringer
Copy link
Contributor

Hello,
One of the challenges of maintaining a large open source project is that sometimes, you can bite off more than you can chew. As the lead maintainer of google-cloud-python, I can definitely say that I have let the issues here pile up.

As part of trying to get things under control (as well as to empower us to provide better customer service in the future), I am declaring a "bankruptcy" of sorts on many of the old issues, especially those likely to have been addressed or made obsolete by more recent updates.

My goal is to close stale issues whose relevance or solution is no longer immediately evident, and which appear to be of lower importance. I believe in good faith that this is one of those issues, but I am scanning quickly and may occasionally be wrong. If this is an issue of high importance, please comment here and we will reconsider. If this is an issue whose solution is trivial, please consider providing a pull request.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: cloudresourcemanager Issues related to the Resource Manager API. priority: p2 Moderately-important priority. Fix may not be included in next release. testing
Projects
None yet
Development

No branches or pull requests

4 participants