[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 over 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.

Hi fellow data professional! This is the 100th week I’m reaching out into the void of the Internet to connect with you in order to democratize data engineering career knowledge. In the golden age of cable TV, shows would celebrate the 100th episode milestone by airing extended content like a 1-hour special for a sitcom that would typically consume 30 minutes. But I know your time is valuable so I’m going to do the opposite and make this a shorter newsletter than normal. Since I live what I...

Hi fellow data professional! For my health I try not to argue with my wife; but when she told me her networking plan I had to push back. Some context. She’s exploring career paths within the multinational corp she works for and wanted to meet with a friend of a family member. The catch? She felt weird about leveraging a personal connection and wanted to reach out cold. This is the wrong approach. Western culture demonizes nepotism but, truthfully, sometimes a connection is so painfully...

Hi fellow data professional! It’s baseball season in the U.S., a game defined by the "on-deck" line up. Before a player takes a big swing at the plate, they are already there, weighted bat in hand, timing the pitcher (who has to move a bit faster now thanks to the pitch clock), fully prepared for their moment. They don’t start looking for their helmet only after the umpire calls them up. In your early career perhaps you're considering "taking a big swing" by applying for that dream role at a...