Skip to content

feat/client elastic load balancing v2 - #229

Merged
floydspace merged 8 commits into
floydspace:betafrom
godu:feat/client-elastic-load-balancing-v2
Aug 29, 2026
Merged

feat/client elastic load balancing v2#229
floydspace merged 8 commits into
floydspace:betafrom
godu:feat/client-elastic-load-balancing-v2

Conversation

@godu

@godu godu commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

What

Adds @effect-aws/client-elastic-load-balancing-v2, generated from the AWS Smithy manifest via the repo's codegen-client flow (51 operations, plus *Stream variants for the paginated ones), with a major changeset so the release pipeline publishes it.

Two changes beyond the usual codegen flow

scripts/generate-client.ts — capitalize the sdk name per word. The service's sdkId is Elastic Load Balancing v2, and the old rule (strip spaces, then capitalize) produced ElasticLoadBalancingv2Client, which the SDK does not export — the real symbol is ElasticLoadBalancingV2Client. Each space-separated word is now capitalized before joining. Every existing client's generated name already has uppercase-initial words (APIGateway, IoTDataPlane, SESv2, ...), so no existing output changes.

@smithy/types bumped to 4.17.2. With resolution-mode=highest, the new client's lockfile entry pulled @smithy/types@4.17.2 while its siblings stayed at 4.16.1. Two copies in the tree break the Service.fromClientAndCommands call with the familiar step "serialize" is not assignable to "initialize" error. pnpm dedupe does not collapse it; pnpm update -r "@smithy/types" does, which is where the lockfile churn and the commons / http-handler ^4.17.2 bumps come from. No source changes were needed for it, and the AWS SDK itself stays at the repo-wide 3.1090.0.

Verification

  • pnpm compile clean across the monorepo
  • pnpm vitest run — 74 test files / 427 tests passing, including the 6 generated for this client
  • pnpm eslint --fix applied

Adds @effect-aws/client-elastic-load-balancing-v2.

The AWS SDK exports `ElasticLoadBalancingV2*`, while the codegen derived
`ElasticLoadBalancingv2*` from the `Elastic Load Balancing v2` sdkId, so the
sdk name is now capitalized per word. Bumping @smithy/types to 4.17.2 keeps a
single copy in the tree, which the new client's transitive deps require.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@changeset-bot

changeset-bot Bot commented Aug 20, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 382fddf

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages
Name Type
@effect-aws/client-elastic-load-balancing-v2 Major
@effect-aws/http-handler Patch
@effect-aws/commons Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@godu godu closed this Aug 20, 2026
@godu godu reopened this Aug 20, 2026
@godu
godu changed the base branch from main to beta August 20, 2026 11:47
godu and others added 7 commits August 20, 2026 14:22
`pnpm docgen` failed on two counts, both predating this branch.

Every generated `*Service$` interface lacked a `@since` tag, which docgen
rejects, so all 62 client packages failed to parse. The tag is added to the
codegen template and to the already-generated files; regenerating a client
whose model still matches the pinned SDK reproduces the patched file exactly.

The `streamFromHttpApi` example still used the Effect 3 API — `@effect/platform`
is not a dependency of `packages/lambda`, and `HttpApiBuilder.api` /
`HttpServer.layerContext` no longer exist. It now mirrors the `fromHttpApi`
example above it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@floydspace
floydspace merged commit 401b544 into floydspace:beta Aug 29, 2026
5 checks passed
@github-actions github-actions Bot mentioned this pull request Aug 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants