jsii

May also be useful for creating automatic language support from a single codebase. For example, Amazon uses JSII to build a typescript library into Python, Go, dotnet, etc. Maybe this tooling will help add PHP to that list. That way you are not maintaining 6 codebases. https://github.com/aws/jsii

The libraries for other supported languages of CDK are built as wrappers for underlying JS or maybe TS code via https://github.com/aws/jsii So all the core CDK code is written first in JS/TS and then stubs for the other languages are added Unfortunately this is often done without consideration for how the other supported langs actually work, and artefacts of e.g. JS lack of support for kwargs leak through This is why e.g. the typing in CDK Python is completely broken - pretty much uniformly the concrete types like "Resource" don't implement their corresponding interface like "IResource" (to a type checker) (There are many other typing niggles like this but that's the most egregious and pervasive one) At the end of the day, having to explicitly cast concrete types as their interface to satisfy type checker is a minor annoyance, albeit a st

Every version of the CDK uses an interop layer and runs on top of the Typescript version https://github.com/aws/jsii And as far as TF supports services before CFT. Guess which is easier for an AWS employee to do - getting the CF service team to support a new service or just contribute to Terraform’s open source project? I know of at least one service where the service team introduced the needed APIs and then an employee of AWS wrote the TF provider and contributed to the project before AWS’s own internal team added it to CFT. Source: former AWS ProServe employee. I am not referring to myself as the author.

Wow, that's kind of cool. Didn't know about that. It is me, or is it weird that this has a hard constructor dependency on Constructs[1], which is pretty much undocumented? At least in golang, this brings in some other dependencies and golang init() reflect code [2], which then depends on interacting with javascript!? [3]... something smells odd here. [1] https://github.com/aws/constructs-go [2] https://github.com/aws/constructs-go/blob/main/constructs/co... [3] https://github.com/aws/jsii/

Have you heard of or explored https://github.com/aws/constructs (related: https://github.com/aws/jsii and https://github.com/aws/aws-cdk)? This is what CDK uses for declarative modeling, but gives the opportunity to use languages/tooling that most devs are already familiar with. CDK8s already uses it as a replacement for yaml (technically, the yaml becomes an implementation detail rather than actually replaced)

So this idea has been on my mind for a while... I absolutely hate writing Open API documents in yaml by hand. GUI tools like StopLight Studio are a bit better, but still don't really cut it for me. I don't like generating it from code either because it tends to clutter everything and devs usually get too confident and don't bother to make sure that the output is good enough. So, ever since I saw the aws-cdk I can't stop thinking that this approach would be a perfect solution for generating Open API docs in a much more dev-friendly way. Here's a list of features that either would work out of the box or with just a bit of effort: - Language bindings for popular languages through jsii (https://github.com/aws/jsii) (same tech behind aws-cdk). - Type checks and autocomplete. - I18n. - Support for js modules and npm packages. - Easy CICD integr