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

Consider switching to Infracost API #36

Open
gdubicki opened this issue Apr 9, 2023 · 2 comments
Open

Consider switching to Infracost API #36

gdubicki opened this issue Apr 9, 2023 · 2 comments

Comments

@gdubicki
Copy link
Contributor

gdubicki commented Apr 9, 2023

I have recently written an internal app that is using Infracost API and it works really well.

Infracost API is a third-party solution, not from GCP, but from a company that focuses on providing accurate cloud infra cost estimations. So they do their best to deal with the price scraping / using Catalog API in the backend and provide a nice GraphQL API in the front.

It's available for free but you can also self-host your own instance.

@Burekasim
Copy link
Collaborator

Hi @gdubicki

Are there any discrepancies between gcpinstances.info and Google Cloud official pricing?

if there is no issue with the pricing, I don't see a reason to rewrite the entire scraper.

@gdubicki
Copy link
Contributor Author

gdubicki commented Apr 9, 2023

No, I haven't noticed any discrepancies.

So sure, there is no need to do this now.

But I think it's worth considering in the future if the scraping would start to require a lot of work to maintain it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants