[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 PipelineToDE Hi past, present or future data professional! I want to share the single most important realization I had back in the summer of 2021. I was burned out, juggling two part-time jobs, trying to plan a wedding, and drowning in full-time job applications. I felt overwhelmed and underprepared as I plunged into a sea of candidates I perceived to be more intelligent and better "fits" than me. My portfolio was full of the usual Titanic, Iris,...

Extract. Transform. Read. A newsletter from PipelineToDE Hi past, present or future data professional! One of the most validating and terrifying professional moments is reaching the final interview round. It is in this context that you meet candidacy’s final boss, who incidentally, usually ends up being your boss' boss. Specifically I’m referring to the department executive responsible for bringing in additional headcount, i.e. you. While this may sound intimidating, the role of the executive...

Extract. Transform. Read. A newsletter from PipelineToDE Hi past, present or future data professional! If you’re a job seeker in the data space, your GitHub portfolio has only one job: To act as a calling card that gets you to the next step of the hiring process. Too often, I review portfolios for potential referrals and see brilliant code buried under structural mistakes that have nothing to do with programming skill. Your GitHub is not just cloud storage for your code; it’s a public display...