Automate site updates? - I can help

[gdubicki]

Hi @Burekasim and the whole team!

Thanks again for this solution. While there are alternatives now, I really like your minimalistic and clear site.

But again I don't feel confident that it shows the up-to-date info because as of writing these words the data update time is 2022-12-18, which is 2.5 weeks ago if you are an optimist ...or last year if you are a pessimist. 😅

Anyway, I wanted to ask what is the progress on automating the updates? I read the comment that's it's on the roadmap from June 2022 but I also remember my ticket from October 2021 about the same thing, so perhaps I can help you with this if you are stuck?

Don't want to brag but I have a lot of experience with various CI/CD solutions, including Github Actions which would make the most sense here probably. (You can check out my work in gitlabform/gitlabform, for example.) I propose to create a site update pipeline running once per day (or on another schedule, if you think that makes more sense).

What do you think?

[Burekasim]

Hi @gdubicki

Regarding pricing:
I might need to clarify the current status, I update the website (manually) when there are price changes, if there are no price changes, there i no update.

At this moment, since December 18, there are no changes in GCP pricing. and because of that - the website is still shows the date from December.

Also - I usually run diff between the latest version and the previous version and there are minor price changes for CUDs in non US/EU regions.

I think we should change the wording from "Last Update" to something else, I'm open for suggestions.

Regarding automation:
I would be glad for any assistance, can you send me your email and we will continue discussing over email

There is a small issue that might affect the automation - if Google adds a new instance family, it will break the scraper.py. script.

[gdubicki]

Regarding pricing:

Thanks for clarification!

I think that when we automate we could think of providing 2 timestamps that we could call f.e. "Last prices check" and "Last update", maybe with a link to your comment to clarify the difference. :)

Then the pipeline could update the "Last prices check" on each run, while the "Last update" only when the data has actually changed.

Regarding automation:

I pinged you on LinkedIn to get in touch.

About that breakage on new instance family add: I think that it's good that it will break! Thanks to that we will get notification about pipeline breaking and we will see that the code needs an update to include the new family. :)