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.

Sign up for GitHub

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

Jump to bottom

Should we map the '/projects/get' API #1136

Closed
tseaver opened this issue Sep 14, 2015 · 2 comments
Closed

Should we map the '/projects/get' API #1136

tseaver opened this issue Sep 14, 2015 · 2 comments
Assignees
@tseaver
Labels
api: dns Issues related to the Cloud DNS API.

Comments

@tseaver
Copy link
Contributor

tseaver commented Sep 14, 2015

See https://cloud.google.com/dns/api/v1/projects/get

The resource consists of read-only information (quotas, mostly) about the project within DNS.

One strategy might be to add a quotas method to the client which fetched and returned the quotas sub-mapping for the project.
@tseaver tseaver added the api: dns Issues related to the Cloud DNS API. label Sep 14, 2015
@dhermes
Copy link
Contributor

dhermes commented Sep 14, 2015

If it's simple to do, I see no reason not to. If it is a lot of work, we can revisit.

@tseaver
Copy link
Contributor Author

tseaver commented Sep 21, 2015

The Client.quotas method does expose all the relevant information.

@tseaver tseaver closed this as completed Sep 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tseaver tseaver

Labels
api: dns Issues related to the Cloud DNS API.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tseaver @dhermes