chore: regenerate models from upstream schemas #11

Merged

stack72 merged 1 commit from automated/regenerate-models into main 2026-05-28 12:18:30 +00:00

Conversation 1 Commits 1 Files changed 7 +162 -26

stack72 commented 2026-05-28 06:08:45 +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 added 1 commit 2026-05-28 06:08:45 +00:00

chore: regenerate models from upstream schemas (2026-05-28) 9a0a2e91e6

stack72 commented 2026-05-28 06:19:42 +00:00

Author

Owner

Copy link

Code Review

Blocking Issues

None.

Suggestions

1. Upgrade descriptions are inaccurate across all four models: Each new upgrade entry uses description: "No schema changes", but each model does include schema changes — new optional fields (NetworkInterface, InstanceRequirements in sagemaker/cluster; per-GPU accelerator fields in dataproc/batches and dataproc/sessions; sizeAboveBytes/sizeBelowBytes in storage/buckets) and InstanceType being relaxed from required to optional in sagemaker/cluster. These are all non-breaking additions, so the pass-through upgradeAttributes: (old) => old is correct. But the description field is misleading. If the codegen pipeline can detect non-breaking field additions, a description like "Added optional fields from upstream schema update" would be more informative for anyone reading the upgrade history.

---

Context on model-only changes: This PR contains no codegen/ changes, but the changed model files are clearly auto-generated output (auto-gen header comment, consistent Zod structure, bot-authored commit from forgejo-actions[bot]). The preceding regeneration commit (563f4073) follows the same pattern — model/ changes only, no codegen/ changes — confirming this is the normal daily upstream schema regeneration workflow where the pipeline is unchanged and only the input schemas from AWS/GCP have evolved.

## Code Review ### Blocking Issues None. ### Suggestions 1. **Upgrade descriptions are inaccurate across all four models**: Each new upgrade entry uses `description: "No schema changes"`, but each model does include schema changes — new optional fields (`NetworkInterface`, `InstanceRequirements` in sagemaker/cluster; per-GPU accelerator fields in dataproc/batches and dataproc/sessions; `sizeAboveBytes`/`sizeBelowBytes` in storage/buckets) and `InstanceType` being relaxed from required to optional in sagemaker/cluster. These are all non-breaking additions, so the pass-through `upgradeAttributes: (old) => old` is correct. But the description field is misleading. If the codegen pipeline can detect non-breaking field additions, a description like `"Added optional fields from upstream schema update"` would be more informative for anyone reading the upgrade history. --- **Context on model-only changes**: This PR contains no `codegen/` changes, but the changed model files are clearly auto-generated output (auto-gen header comment, consistent Zod structure, bot-authored commit from `forgejo-actions[bot]`). The preceding regeneration commit (`563f4073`) follows the same pattern — `model/` changes only, no `codegen/` changes — confirming this is the normal daily upstream schema regeneration workflow where the pipeline is unchanged and only the input schemas from AWS/GCP have evolved.

stack72 merged commit 582d894e3a into main 2026-05-28 12:18:30 +00:00

stack72 deleted branch automated/regenerate-models 2026-05-28 12:18:31 +00:00

stack72 referenced this pull request from a commit 2026-05-28 12:18:32 +00:00

chore: regenerate models from upstream schemas (#11)

stack72 referenced this pull request 2026-06-01 06:20:41 +00:00

chore: regenerate models from upstream schemas #21

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

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

No description provided.