chore: regenerate models from upstream schemas #51

Merged

stack72 merged 1 commit from automated/regenerate-models into main 2026-06-12 09:34:22 +00:00

Conversation 2 Commits 1 Files changed 109 +8906 -433

stack72 commented 2026-06-11 06:12:20 +00:00

Owner

Copy link

Summary

Automated regeneration of extension models from upstream provider schemas.

Schema Sources

• AWS: CloudFormation Resource Schema
• GCP: Google Discovery Documents
• Hetzner: Hetzner Cloud OpenAPI spec
• DigitalOcean: DigitalOcean OpenAPI spec

Review Notes

• Files under model/ are auto-generated — review the manifest.yaml diffs for version changes
• CalVer versioning with content-based change detection ensures versions only bump when content changes
• Publishing happens automatically when this PR is merged (via the publish workflow)

## Summary Automated regeneration of extension models from upstream provider schemas. ### Schema Sources - **AWS**: CloudFormation Resource Schema - **GCP**: Google Discovery Documents - **Hetzner**: Hetzner Cloud OpenAPI spec - **DigitalOcean**: DigitalOcean OpenAPI spec ### Review Notes - Files under `model/` are auto-generated — review the `manifest.yaml` diffs for version changes - CalVer versioning with content-based change detection ensures versions only bump when content changes - Publishing happens automatically when this PR is merged (via the publish workflow)

stack72 commented 2026-06-11 06:24:17 +00:00

Author

Owner

Copy link

Code Review

Blocking Issues

None.

Summary

All 70 changed files are under model/ and were produced by the codegen pipeline. Every modified and newly added .ts file carries the standard auto-generated header (// Auto-generated extension model … Do not edit manually. Re-generate with: deno task generate:aws or deno task generate:gcp), and the Zod schema structure is consistent with pipeline output throughout.

The PR contains a single commit (chore: regenerate models from upstream schemas (2026-06-11)) and follows the same recurring pattern as previous regeneration commits in the repo history. No codegen/ files needed to change because the pipeline itself was not modified — only the upstream CloudFormation/GCP schemas changed, producing updated model output.

Changes observed:

• New AWS services / resources: model/aws/bcm/ (entirely new package — AWS::BCM::Dashboard), model/aws/apigatewayv2/stage.ts, model/aws/appstream/stack_fleet_association.ts, model/aws/sagemaker/mlflow_app.ts
• Updated AWS models: eks/cluster.ts (new EtcdPlacement/EtcdInstanceType fields on OutpostConfig), aps/workspace.ts, logs/delivery_source.ts, neptune/dbcluster.ts, observabilityadmin/telemetry_enrichment.ts, appstream/stack.ts
• Updated GCP models: compute/ (instance templates, instances, instance group managers, interconnects, machine images, TCP proxies), run/ (services, revisions, worker pools — new sandboxes/sandboxLauncher fields), chat/spaces_messages.ts, cloudchannel/, domains/registrations.ts, hypercomputecluster/clusters.ts, merchantapi/accounts_products.ts, saasservicemgmt/, workloadmanager/
• Manifest files: all updated with new CalVer versions (2026.06.11.1) and matching releaseNotes entries

All manifest version bumps and release-note entries accurately reflect the file-level additions and updates. No hand-edited code, no security concerns, no test gaps (generated model files do not require their own tests).

## Code Review ### Blocking Issues None. ### Summary All 70 changed files are under `model/` and were produced by the codegen pipeline. Every modified and newly added `.ts` file carries the standard auto-generated header (`// Auto-generated extension model … Do not edit manually. Re-generate with: deno task generate:aws` or `deno task generate:gcp`), and the Zod schema structure is consistent with pipeline output throughout. The PR contains a single commit (`chore: regenerate models from upstream schemas (2026-06-11)`) and follows the same recurring pattern as previous regeneration commits in the repo history. No `codegen/` files needed to change because the pipeline itself was not modified — only the upstream CloudFormation/GCP schemas changed, producing updated model output. Changes observed: - **New AWS services / resources:** `model/aws/bcm/` (entirely new package — `AWS::BCM::Dashboard`), `model/aws/apigatewayv2/stage.ts`, `model/aws/appstream/stack_fleet_association.ts`, `model/aws/sagemaker/mlflow_app.ts` - **Updated AWS models:** `eks/cluster.ts` (new `EtcdPlacement`/`EtcdInstanceType` fields on `OutpostConfig`), `aps/workspace.ts`, `logs/delivery_source.ts`, `neptune/dbcluster.ts`, `observabilityadmin/telemetry_enrichment.ts`, `appstream/stack.ts` - **Updated GCP models:** `compute/` (instance templates, instances, instance group managers, interconnects, machine images, TCP proxies), `run/` (services, revisions, worker pools — new `sandboxes`/`sandboxLauncher` fields), `chat/spaces_messages.ts`, `cloudchannel/`, `domains/registrations.ts`, `hypercomputecluster/clusters.ts`, `merchantapi/accounts_products.ts`, `saasservicemgmt/`, `workloadmanager/` - **Manifest files:** all updated with new CalVer versions (`2026.06.11.1`) and matching `releaseNotes` entries All manifest version bumps and release-note entries accurately reflect the file-level additions and updates. No hand-edited code, no security concerns, no test gaps (generated model files do not require their own tests).

stack72 force-pushed automated/regenerate-models from 9e934eb55a to f1bd2bffea 2026-06-12 06:12:37 +00:00 Compare

stack72 commented 2026-06-12 06:24:24 +00:00

Author

Owner

Copy link

Code Review

Blocking Issues

None.

Suggestions

None.

---

All 109 changed files are auto-generated model files under model/. The commit message ("chore: regenerate models from upstream schemas (2026-06-12)") matches the established pattern for schema-refresh PRs (#44, #47, #48). All manifests carry the # Auto-generated manifest header confirming they are codegen output.

Notable changes:

• Three new service packages added: model/aws/awsexternalanthropic/, model/aws/bcm/, model/gcp/cloudproductregistry/
• Updates to existing models across AWS (apigatewayv2, appstream, aps, eks, logs, neptune, observabilityadmin, opensearchserverless, sagemaker) and GCP (artifactregistry, ces, chat, cloudchannel, compute, domains, gkehub, hypercomputecluster, logging, merchantapi, monitoring, networkservices, pubsub, run, saasservicemgmt, workloadmanager)

No codegen pipeline changes are required here — the pipeline itself is unchanged; only the upstream schemas changed, producing new/updated model output. This is consistent with how previous schema-refresh PRs in this repo operate.

## Code Review ### Blocking Issues None. ### Suggestions None. --- All 109 changed files are auto-generated model files under `model/`. The commit message ("chore: regenerate models from upstream schemas (2026-06-12)") matches the established pattern for schema-refresh PRs (#44, #47, #48). All manifests carry the `# Auto-generated manifest` header confirming they are codegen output. Notable changes: - Three new service packages added: `model/aws/awsexternalanthropic/`, `model/aws/bcm/`, `model/gcp/cloudproductregistry/` - Updates to existing models across AWS (apigatewayv2, appstream, aps, eks, logs, neptune, observabilityadmin, opensearchserverless, sagemaker) and GCP (artifactregistry, ces, chat, cloudchannel, compute, domains, gkehub, hypercomputecluster, logging, merchantapi, monitoring, networkservices, pubsub, run, saasservicemgmt, workloadmanager) No codegen pipeline changes are required here — the pipeline itself is unchanged; only the upstream schemas changed, producing new/updated model output. This is consistent with how previous schema-refresh PRs in this repo operate.

stack72 merged commit 65b8090cdc into main 2026-06-12 09:34:22 +00:00

stack72 deleted branch automated/regenerate-models 2026-06-12 09:34:22 +00:00

stack72 referenced this pull request from a commit 2026-06-12 09:34:23 +00:00

chore: regenerate models from upstream schemas (#51)

stack72 referenced this pull request 2026-06-14 06:23:49 +00:00

chore: regenerate models from upstream schemas #52

stack72 referenced this pull request 2026-06-16 06:23:32 +00:00

chore: regenerate models from upstream schemas #55

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!51

No description provided.