buildpacks VS faas-cli

You're better off using Cloud Run. In some ways, it's easier than App Engine. You can use a buildpack (blog, blog, GitHub) to automatically build a docker image with Go using the code you provide. You can then configure Cloud Run to allow up to 60 minutes of time per invocation.

Under the covers this uses Google Buildpacks to create a container image from your app: https://github.com/GoogleCloudPlatform/buildpacks

Cloud Build is indirectly called to containerize your app. One of its core components is Google Cloud Buildpacks, which automatically builds a production-ready container image from your source code. Here are the main steps:

This explicitly uses the Buildpacks provided by Google. You can find more information about these on Github

The function is containerized using Google Cloud buildpacks.

As for being able to run your own instance of things in isolation, that really depends on the fidelity you want. Firebase has an emulator you could use, and Cloud Functions/AppEngine can be built into docker images locally using the public buildpacks (but won't have the full suite of attached services), but I'd probably recommend good service mocks/stubs/fakes your services plus a pipeline that spins up a full project with Terraform, runs integration tests, then tears it down for e2e testing.

(New-Object System.Net.WebClient).DownloadFile("https://github.com/openfaas/faas-cli/releases/download/$version/faas-cli.exe", "faas-cli.exe")

faas-cli - https://github.com/openfaas/faas-cli

Then I installed the OpenFaaS CLI.

We will create a function that will be packaged in a container using faas-cli, the CLI for use with OpenFaaS. Although the CLI is designed to be used to build and deploy functions to OpenFaaS, it has worked for me outside of OpenFaaS. I use it with Knative and now DigitalOcean App Platform. It has allowed me to write a handler file and the CLI does the rest to create a Docker image and upload it to a registry.