count
gcr-cleaner
Our great sponsors
| count | gcr-cleaner | |
|---|---|---|
| 2 | 3 | |
| 27 | 796 | |
| - | 0.0% | |
| 0.0 | 5.6 | |
| over 1 year ago | about 1 month ago | |
| Go | Go | |
| - | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
count
-
AWS Lambda Terraform Cookbook with working examples
I probably should add a terraform based approach to deploying my "count" HTTP API here: https://github.com/kaihendry/count
-
Show HN: AWS Lambda Terraform Cookbook with working examples
https://github.com/kaihendry/count/blob/sam/template.yml
All in one file.
gcr-cleaner
-
Container registry vs artifact ?
I also use https://github.com/GoogleCloudPlatform/gcr-cleaner
-
Tell HN: Google Cloud suspended our production projects at 1am on Saturday
> You're right that this functionality seems to not be built into the Artifact Registry backend (and that's weird†), but it does still exist: see https://github.com/GoogleCloudPlatform/gcr-cleaner (found linked from https://cloud.google.com/artifact-registry/docs/docker/manag...), and specifically the `keep` flag for it.
No, it does not "exist". It's either builtin and then it exists, or it doesn't. What you linked is a way for me to build it myself. And I found this AND this solution is even linked in the years old Google ticket. And guess what, they didn't build it. On AWS no problem. As I said: years behind.
Sure, I can setup my own cron job (or here cloud run function / github action). But that's not what I expect from a leading cloud vendor. This is not a niche feature!
Please don't defend it, Google doesn't deserve it. Credits to whoever build the 3rd party solution, but Google really failed here.
> Depending on how you design the client, it can also "mandate manual usage" — i.e. ensure that the developer is interactively running the process for the process to proceed
Just no.
Let's face it: Google is just too incompetent to do it. Not the developers there, but the company as a whole in the way it is organized. Even IF it were as you said and it would be a philosophy, they could say that close the ticket, but it's still open.
I can list you dozens of similar things with GCP and related Google services.
-
Delete Untagged Images on Google Cloud
I've seen a few ways to tackle this issue, notably GCR Cleaner, which is mentioned in Google's Container Registry's official documentation.
What are some alternatives?
terraform-aws-lambda - Terraform module, which takes care of a lot of AWS Lambda/serverless tasks (build dependencies, packages, updates, deployments) in countless combinations 🇺🇦
go-containerregistry - Go library and CLIs for working with container registries
sheets-url-shortener - A simple short URL redirect service built on top of Google Sheets, and runs for cheap on Google Cloud Run serverless.
cloud-run-faq - Unofficial FAQ and everything you've been wondering about Google Cloud Run.
lambda-the-terraform-way - AWS Lambda using Terraform., an Introductory Cookbook
terraform-provider-openfaas - Terraform OpenFaaS provider
manifest-tool - Command line tool to create and query container image manifest list/indexes
nixery - Container registry which transparently builds images using the Nix package manager. Canonical repository is https://cs.tvl.fyi/depot/-/tree/tools/nixery