|about 1 month ago||5 days ago|
|MIT License||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.
How to use store_accessor for nested JSON in rails
2 projects | /r/rails | 14 Mar 2023
https://github.com/jrochkind/attr_json (by me)
Is JSONB + Postgres still a viable way of storing varying attributes?
7 projects | /r/rails | 8 Feb 2023
I myself maintain one solution meant for rails attributes stored in a json column, at https://github.com/jrochkind/attr_json
How to implement user options
2 projects | /r/rails | 4 Nov 2022
One of these two should do the trick: https://github.com/jrochkind/attr_json https://github.com/DmitryTsepelev/store_model
The Nosql Store That Everyone Ignored
4 projects | news.ycombinator.com | 5 Sep 2021
attr_json VS jsonb_accessor - a user suggested alternative
2 projects | 8 Aug 2021
jsonb_accessor - typed jsonb backed fields to your ActiveRecord models.
2 projects | /r/ruby | 24 May 2021
I also have a similar "competing" in some ways gem at: https://github.com/jrochkind/attr_json
5 projects | news.ycombinator.com | 20 Apr 2021
Some relational databases like Postgres and MySQL support JSON columns. This is useful if, for example, you want to create an ecommerce application with a products table with many variations - what is called Single Table Inheritance (STI). You can have some regular columns for the common attributes, and a JSON column for the specific ones.
If your app is built with Rails, you can use this library to help you on that (I'm not affiliated with it): https://github.com/jrochkind/attr_json
I think GCP is better than AWS – by Fernando Villalba
6 projects | news.ycombinator.com | 25 Oct 2023
how would any reasonable person know what https://registry.terraform.io/providers/hashicorp/google/5.3... to enable without (a) trying it and squinting at the error message (b) clicking on the <> then realizing it, also, does not mention run.googleapis.com, click on "supported service endpoints" <https://cloud.google.com/run/docs/reference/rest#rest_endpoi...> and only then learning about https://cloud.google.com/run/docs/reference/rest#service:-ru...
Repeat for https://registry.terraform.io/providers/hashicorp/google/5.3... although in both cases I guess the astute reader may have spotted the run.googleapis.com in the forbidden service labels and cloudidentity.googleapis.com in the example
Since, to the best of my knowledge those bindings are auto generated <https://github.com/GoogleCloudPlatform/magic-modules#magic-m...>, I would hypothesize it is not insurmountable drop in the seemingly existing declaration of APIs required: https://github.com/GoogleCloudPlatform/magic-modules/blob/7d... https://github.com/GoogleCloudPlatform/magic-modules/blob/7d...
Terraform Plugin Framework Development: How to implement nested attributes?
5 projects | /r/Terraform | 11 Apr 2022
In the case of the Google Cloud Platform provider, folks at Google built magic modules with the explicit goal of being able to generate schemas and behaviors for a Terraform provider and for other systems with similar needs. Since the vendor was explicitly aiming to support Terraform, this was the most ideal case where the schema could be designed to contain all of the information needed to generate a functional, usable provider.
Terraform 1.0 Release
33 projects | news.ycombinator.com | 8 Jun 2021
For GCP, both ansible modules and terraform modules are actually generated from https://github.com/GoogleCloudPlatform/magic-modules, so their "production readiness" are the same.
I understand that mitchellh himself personally created a bunch of cloud modules for terraform at the beginning, and those were likely of higher quality than whatever created by some internal developers assigned by Google/Microsoft, and might be slightly better than the AWS modules maintained by community.
Anyway, when it comes to ansible versus terraform, we shall move the discourse to states management instead. With ansible, you don't have to deal with states, but will need to clean up the cloud resources separately. With terraform, you can use the tool to clean up the cloud resources easily, but then you also have the headache of managing states. Plus, whenever you change something, there is always the nagging feeling that it will do a destroy/recreate instead of an in-place update.
5 projects | news.ycombinator.com | 20 Apr 2021
The Terraform provider for Google Cloud uses partial autogeneration, here is the repo that does the autogeneration for multiple automation tools:
What are some alternatives?
jsonb_accessor - Adds typed jsonb backed fields to your ActiveRecord models.
terraform-ls - Terraform Language Server
tf2pulumi - A tool to convert Terraform projects to Pulumi
desktop-ansible - Ansible Playbooks to install Arch on my PC from scratch
terraform-cdk - Define infrastructure resources using programming constructs and provision them using HashiCorp Terraform
pulumi-provider-boilerplate - Boilerplate showing how to create a native Pulumi provider
pulumi-terraform-bridge - A library allowing providers built with the Terraform Plugin SDK to be bridged into Pulumi.
terraform-lsp - Language Server Protocol for Terraform
terraform-provider-meraki - Terraform provider for the Meraki Dashboard API
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
superstore - ActiveModel for JSONB documents