feat(ruby): add Ruby language bindings for AWS CDK - #38248
Draft
omarqureshi wants to merge 2 commits into
Draft
Conversation
github-actions
Bot
added
beginning-contributor
aws-cdk-automation
requested changes
Jul 4, 2026
Collaborator
There was a problem hiding this comment.
The pull request linter fails with the following errors:
❌ Features must contain a change to an integration test file and the resulting snapshot.
If you believe this pull request should receive an exemption, please comment and provide a justification. A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed, add Clarification Request to a comment.
✅ A exemption request has been requested. Please wait for a maintainer's review.
11 tasks
omarqureshi
force-pushed
the
ruby-language-bindings
branch
from
July 4, 2026 11:53
7375094 to
731852d
Compare
omarqureshi
changed the title
Adds Ruby language target configuration (.jsiirc.json module/gem naming and acronyms) across aws-cdk-lib, in support of jsii Ruby bindings.
omarqureshi
force-pushed
the
ruby-language-bindings
branch
from
July 4, 2026 12:28
731852d to
9e34b31
Compare
Author
|
Exemption Request - This PR contains no runtime code changes, it is pure configuration and as such no integration tests or changes to snapshots have been made. |
aws-cdk-automation
added
the
pr-linter/exemption-requested
aws-cdk-automation
temporarily deployed
to
automation
July 4, 2026 12:34 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
aws-cdk-automation
temporarily deployed
to
automation
July 4, 2026 12:34 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
…n bad .jsiirc
writeJsiiRc only preserved an existing targets.ruby, so a brand-new
service submodule generated after a rebase would ship with no ruby module
name, silently breaking the invariant that every submodule has one. It
now derives { module: "AWSCDK::<Name>" } when absent, reading the root
module and acronym list from aws-cdk-lib's package.json at derivation
time — the single source of truth; nothing is hardcoded.
The conformance test proves the rules against reality: derivation
reproduces the committed .jsiirc.json ruby module for every regular
scope-map submodule, with the 16 genuinely hand-chosen irregulars
enumerated and asserted as committed-value-wins overrides (existing
declarations are always preserved verbatim).
The JSON-parse swallow is gone: an unreadable or invalid .jsiirc.json now
throws with the file path instead of silently dropping ruby targets.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #38247
Warning
Draft — CI is expected to be red, by design. Ruby code generation requires a jsii release with Ruby target support, which is not yet published (tracked in aws/jsii#5178). Until it ships, jsii-pacmak has no Ruby target on the released toolchain, so packaging/codegen checks will fail. End-to-end generation + Ruby gem publishing have already been validated against a pre-release build of the compiler. Once the compiler is released this will go green.
Reason for this change
Add Ruby as a first-class supported language for AWS CDK, alongside TypeScript, Python, Java, C#/.NET and Go. Ruby-centric infrastructure teams currently maintain a parallel toolchain in another language or avoid CDK entirely. Demand has been long-standing — the original request has been open since 2018 and is one of the most-reacted language asks.
Design is captured in RFC 0935: Ruby language bindings — tracking issue aws/aws-cdk-rfcs#935 (full RFC text).
Description of changes
Strictly additive — no changes to existing languages, no breaking changes.
.jsiirc.jsonRuby target configuration acrossaws-cdk-lib(329 modules): each gains arubytarget with its module name (root namespaceAWSCDK, idiomatic casing, AWS-prefix de-duplication — e.g.aws-s3→AWSCDK::S3::Bucket). Naming follows RFC 0935; version suffixes use lowercasev(AWSCDK::WAFv2, matching theIPv4/IPv6convention).tools/@aws-cdk/spec2cdk(submodule-files.ts): when regenerating a module's.jsiirc.json, preserve an existing hand-authoredrubytarget (java/dotnet/python remain auto-derived). Without this,gen-cdkwould wipe the Ruby blocks.The enabling jsii work (compiler +
jsii-pacmakRuby target +@jsii/ruby-runtime) is in aws/jsii#5178.Describe any new or updated permissions being added
None — this is code-generation configuration only; no runtime/IAM changes.
Description of how you validated changes
aws-cdk-lib).rbs validatein the jsii runtime test suite (see feat(ruby): Ruby language bindings jsii#5178).Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license