[ETR #17] Warning: Your Google Cloud Function Might Fail Next Week


Extract. Transform. Read.

A newsletter from Pipeline

Technically, this title is misleading. Not because your Google Cloud Function won’t fail. It may.

And we’ll get to that.

I promise.

But because Google Cloud Functions are now called Google Cloud Run functions, selecting a name that reflects a fusion between Cloud Run and Cloud Functions, which were previously two distinct Google Cloud Platform products. While both products leverage serverless architecture to run code, Cloud Run was geared more toward those developing apps while Cloud Functions was more of a “quick and dirty” way to get simpler scripts, like ETL pipelines, into production.

No matter what GCP calls this product, you’ll still be able to run scripts using a serverless configuration. As a bonus, you’ll now be able to use NVIDIA-based CPUs to boost runtime compute power. To leverage this though, you’ll need to upgrade to a gen 2 cloud function.

With many new releases comes obsolescence. This case is no different. Effective October 14th, Google Cloud Functions (excuse me, Google Cloud Run functions), will no longer support Python 3.8, as Python itself is ending support for 3.8 in the same time frame.


To properly upgrade your functions, take these steps:

  • Choose a 3.x release > 8 that is compatible with your dependencies
  • Check your Python version
  • Download a version > 3.8
  • Update the runtime in your YAML deployment file

If you need to go into more depth with updating runtimes or other aspects of deployment, you can learn to deploy a cloud function in 5 days.

It’s 100% free and comes with access to a dedicated GitHub repository.

Enroll here.

I want to make sure I keep you sufficiently updated, so here are this week’s links:

Until next time—thanks for ingesting,

-Zach Quinn

Extract. Transform. Read.

Reaching 20k+ readers on Medium and nearly 3k learners by email, I draw on my 4 years of experience as a Senior Data Engineer to demystify data science, cloud and programming concepts while sharing job hunt strategies so you can land and excel in data-driven roles. Subscribe for 500 words of actionable advice every Thursday.

Read more from Extract. Transform. Read.

Extract. Transform. Read. A newsletter from Pipeline Hi past, present or future data professional! A data science manager recently gave me some blunt, liberating advice over coffee: “If a team lead really cares what cloud technology you know (AWS, GCP, etc.) and doesn’t consider transferable experience… run.” This critical advice, which informs the conclusion of my soon-to-be-released ebook on data engineering project development, cuts to the core of a major problem in data hiring: The...

Extract. Transform. Read. A newsletter from Pipeline Hi past, present, or future data professional! For all of the latest tech trends that come and go, one idea has always persisted in the tech world: Longevity isn’t cool. I say this because I recently hit a professional milestone: 4 years with my current organization. My career trajectory offers a counter-narrative to the “job-hopping is the only way to succeed” mentality. My goal isn't to convince you to be a “lifer,” but to demonstrate...

Extract. Transform. Read. A newsletter from Pipeline Hi past, present or future data professional!The most dramatic dataset in the U.S. right now is labor data. Marred by revisions, official firings and general distrust, when the dust clears, U.S. unemployment hovers around 4%. The tech sector, specifically, ticked up from an all-time low to 3%, with overall jobs and postings decreasing significantly. While 3% is far from the industry’s record 5.7% set earlier this year, it is concerning.Ok....