Activity, over time
Daily GitHub activity and social mentions.
Mentions
Daily posts linking to this repository
Attention
Daily stars & forks
Star accumulation
Cumulative stars
Pull requests
Daily opens & merges
Conversations
Daily issues & comments
Community
Daily accounts & reviews
Trending history
Daily top 10 · last 90 days · UTC
Mentions
Stars
Forks
Contributors
Latest stargazers
The last 10 distinct accounts we observed this year.
Most active participants
PR, issue, comment & review events in the past year.
Packages
Scan pending.
Live mentions badge
Show how many posts mention your project in the last 30 days.
Live mentions · last 30 days
Mentions
The IaC Wars Have a Shared Blast Radius | Pulumi's new Google Cloud release Infrastructure engineers can spend an impressive amount of time debating which language should describe a load balancer. The load balancer remains remarkably indifferent. HCL or TypeScript. Declarative configuration or a general-purpose language. Terraform, OpenTofu, or Pulumi. Those choices matter. They affect how teams compose infrastructure, test abstractions, and manage deployments. But the debate often stops one layer too early. The code on your screen is not the entire system changing your cloud. Between that code and the API sits a provider, carrying schemas, defaults, validation rules, and lifecycle behavior. Change that dependency and the meaning of otherwise familiar configuration can change with it. This week's useful reminder is Pulumi's Google Cloud provider v10 announcement, published October 6. The v10.0.0 release landed October 5 and tracks upstream terraform-provider-google-beta v8.5.0. The news is not that Pulumi has secretly become Terraform. It has not. The news is that a competitive IaC landscape can still share consequential dependencies. Full Article: terraformacademy.app