Tim Sweña (Swast)

If we want to use Terraform for this, I'd suggest using a [`for_each` block](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings) over a [`fileset` list](https://www.terraform.io/docs/configuration/functions/fileset.html) of `cloudbuild.yaml` files on the config I added in #467 The [gcs...

@jaketf has a PR open for this in https://github.com/GoogleCloudPlatform/professional-services/pull/521

@jaketf Do we have an owner for this tool? I don't particularly want to be "it" just because I was last to touch it. (Also, I suspect this is due...

Filed googleapis/python-kms#37 so that we can eventually migrate to `google-cloud-kms` 2.0

If we make the linter docker image public, we can remove the need for the terraform step. (I think someone may have already done this)

One issue with caching builds is that it can leave us without knowing if a package update / installation is broken, as we'd only update that layer of the image...

When `npm audit` is run, it creates the `node_modules` directory, delaying other tests. > In general, we should probably exclude any directories listed in .gitignore. That's a good idea.

Note: CODEOWNERS also supports GitHub teams. That may be a more scalable solution.

Re: running in each sub-dir, it doesn't appear to be natively supported. It required some bash magic here: https://github.com/GoogleCloudPlatform/cloud-builders-community/blob/master/cloudbuild.yaml but should be easy enough to adapt 🤞

> Had the same issue on latest jupyter lab v3.3.0 @Nriver I was able to fix this issue by installing `jupyterlab_widgets` in addition to `ipywidgets`. See: https://ipywidgets.readthedocs.io/en/latest/user_install.html#installing-in-jupyterlab-3-x Earlier versions of...