-
Notifications
You must be signed in to change notification settings - Fork 15
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
Feature Request: get info as API? #28
Comments
Hi @MaxPowerWasTaken , I thought about it, and consulted internally with colleagues and at the moment, I don't think we will build an API for gcpinstances.info. But, if you are willing to write an API, we can provide the hosting for that API. |
ok thanks for the response Burekasim. I'll try and find some time to take a swing at it; I think you all have done the hardest part already by pulling all the relevant info together into one place. |
Hey so as I start to think about how I'd design the API, I first thought about how often I want to pull fresh data from gcpinstances.info, which made me wonder how often the data on the underlying web page refreshes. Right now on 6/6 the page says Thanks! |
I update the data manually, every 10 days on average. sometimes there are no updates and it can take 30-40 days until the next update (from Google). I plan to automate this procedure and use google billing api instead of gcp calculator, it will happen in a few months. |
Thanks for the response @Burekasim. I think it sounds to me now like since there is already a gcp billing api, there's probably not much to be added by my writing a new API on top of the existing manually-updated website. So unless I'm missing something, I'll probably not do this after all. But thanks again for maintaining such a cool resource and for the answers here. |
I'd like pull this information programmatically (to e.g. select a machine type based on user requested vCPU, RAM, etc). Do you have any interest in supporting an API for this info, or would the API just be to scrape it? Thanks for an awesome resource!
The text was updated successfully, but these errors were encountered: