Skip to content

chore: regenerate models from upstream schemas#110

Open
stack72 wants to merge 1 commit intomainfrom
automated/regenerate-models
Open

chore: regenerate models from upstream schemas#110
stack72 wants to merge 1 commit intomainfrom
automated/regenerate-models

Conversation

@stack72
Copy link
Copy Markdown
Contributor

@stack72 stack72 commented Apr 27, 2026

Summary

Automated regeneration of extension models from upstream provider schemas.

Changes

  • aws: 13 files changed
  • gcp: 5 files changed
  • digitalocean: 2 files changed

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 stack72 force-pushed the automated/regenerate-models branch from 9967e5b to 627df1e Compare April 28, 2026 07:02
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.

1 participant