attr_json VS terraform-cdk

https://github.com/jrochkind/attr_json (by me)

I myself maintain one solution meant for rails attributes stored in a json column, at https://github.com/jrochkind/attr_json

One of these two should do the trick: https://github.com/jrochkind/attr_json https://github.com/DmitryTsepelev/store_model

I also have a similar "competing" in some ways gem at: https://github.com/jrochkind/attr_json

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

At first I tested it to deploy an OVHcloud Managed Kubernetes Service (MKS) with a Node Pool. And step by step, it worked. I even created a Pull Request (PR) in the terraform-cdk repository to add it as an example ☺️.

I'll be trying more sample app deployments with CDK and maybe even explore CDK for Terraform.

You can use CDK with other providers using https://github.com/hashicorp/terraform-cdk

In my experience, CDK is far better than Pulumi, especially if you're mostly going to be using AWS.

I, personally, prefer Crossplane Composite Functions on top of CDK8S, but had dropped CDKTF due to bloat. You can actually manage Kubernetes updates/upgrade lifecycle with Crossplane, as well.

I was going to recommend Pulumi, but looks like CDK for Terraform is still being kept up to date.

Avoid Pulumi, get directly to source and use https://github.com/hashicorp/terraform-cdk