chore: regenerate AWS models from upstream schemas #62

Merged

stack72 merged 1 commit from automated/regenerate-models-aws into main 2026-06-23 23:16:03 +00:00

Conversation 1 Commits 1 Files changed 22 +1020 -44

stack72 commented 2026-06-23 22:57:55 +00:00

Owner

Copy link

Summary

• Regenerated AWS models from latest CloudFormation Resource Schemas (2026-06-23)
• 10 updated models across amazonmq, bedrockagentcore, cognito, connect, ecs, eks, lambda, msk, pcs, ram
• 2 new Lambda models: microvm_image, network_connector
• All updated models have version 2026.06.23.1 with upgrade entries; new models have matching version, no upgrades (first version)

Changes

Service	Model	Type
amazonmq	broker	Updated
bedrockagentcore	harness	Updated
cognito	user_pool_domain	Updated
connect	task_template	Updated
ecs	service	Updated
eks	cluster	Updated
lambda	layer_version	Updated
lambda	microvm_image	New
lambda	network_connector	New
msk	replicator	Updated
pcs	cluster	Updated
ram	resource_share	Updated

Test plan

• CI type-checking passes for all changed services
• Publishing auto-triggers on merge via publish workflow

## Summary - Regenerated AWS models from latest CloudFormation Resource Schemas (2026-06-23) - 10 updated models across amazonmq, bedrockagentcore, cognito, connect, ecs, eks, lambda, msk, pcs, ram - 2 new Lambda models: microvm_image, network_connector - All updated models have version `2026.06.23.1` with upgrade entries; new models have matching version, no upgrades (first version) ## Changes | Service | Model | Type | |---------|-------|------| | amazonmq | broker | Updated | | bedrockagentcore | harness | Updated | | cognito | user_pool_domain | Updated | | connect | task_template | Updated | | ecs | service | Updated | | eks | cluster | Updated | | lambda | layer_version | Updated | | lambda | microvm_image | **New** | | lambda | network_connector | **New** | | msk | replicator | Updated | | pcs | cluster | Updated | | ram | resource_share | Updated | ## Test plan - [ ] CI type-checking passes for all changed services - [ ] Publishing auto-triggers on merge via publish workflow

stack72 added 1 commit 2026-06-23 22:57:55 +00:00

chore: regenerate AWS models from upstream schemas (2026-06-23) ... 9fa1ed3998

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

stack72 commented 2026-06-23 23:10:00 +00:00

Author

Owner

Copy link

Code Review

All 22 changed files are under model/ and are auto-generated. Per review scope rules, model file content is not reviewed directly. The review focuses on whether these changes are legitimate (generated, not hand-edited) and whether any codegen/ changes were expected.

Blocking Issues

None.

Model-only changes without codegen/ changes: The review criteria flag this pattern as potentially indicating hand-edited generated code. However, this PR is a legitimate upstream schema regeneration:

• The commit message is chore: regenerate AWS models from upstream schemas (2026-06-23), matching the project's documented regeneration workflow (deno task fetch-schema:aws && deno task generate:aws).
• Every changed file carries the // Auto-generated extension model and // Do not edit manually. Re-generate with: deno task generate:aws headers.
• The two new model files (microvm_image.ts, network_connector.ts) have complete generator-pattern structure (copyright header, auto-gen comment, deno-lint-ignore-file no-explicit-any, standard schema/model export shape).
• Prior regeneration PRs in this repo (#55, #59, #60) follow the identical pattern — model/ changes only, no codegen/ changes — confirming this is the expected operational workflow when upstream AWS CloudFormation schemas change but the generator itself does not.

Suggestions

None.

## Code Review All 22 changed files are under `model/` and are auto-generated. Per review scope rules, model file content is not reviewed directly. The review focuses on whether these changes are legitimate (generated, not hand-edited) and whether any codegen/ changes were expected. ### Blocking Issues None. **Model-only changes without codegen/ changes:** The review criteria flag this pattern as potentially indicating hand-edited generated code. However, this PR is a legitimate upstream schema regeneration: - The commit message is `chore: regenerate AWS models from upstream schemas (2026-06-23)`, matching the project's documented regeneration workflow (`deno task fetch-schema:aws && deno task generate:aws`). - Every changed file carries the `// Auto-generated extension model` and `// Do not edit manually. Re-generate with: deno task generate:aws` headers. - The two new model files (`microvm_image.ts`, `network_connector.ts`) have complete generator-pattern structure (copyright header, auto-gen comment, `deno-lint-ignore-file no-explicit-any`, standard schema/model export shape). - Prior regeneration PRs in this repo (#55, #59, #60) follow the identical pattern — model/ changes only, no codegen/ changes — confirming this is the expected operational workflow when upstream AWS CloudFormation schemas change but the generator itself does not. ### Suggestions None.

stack72 merged commit ae1f92a15f into main 2026-06-23 23:16:03 +00:00

stack72 deleted branch automated/regenerate-models-aws 2026-06-23 23:16:03 +00:00

stack72 referenced this pull request from a commit 2026-06-23 23:16:05 +00:00

chore: regenerate AWS models from upstream schemas (#62)

stack72 referenced this pull request 2026-06-24 00:06:09 +00:00

chore: regenerate Cloudflare models from upstream schemas #65

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

swamp-club/swamp-extensions!62

No description provided.