chore: regenerate models from upstream schemas #44

Merged

stack72 merged 1 commit from automated/regenerate-models into main 2026-06-08 16:13:09 +00:00

Conversation 1 Commits 1 Files changed 263 +1530 -635

stack72 commented 2026-06-08 06:12:12 +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-06-08 06:12:12 +00:00

chore: regenerate models from upstream schemas (2026-06-08) e1ec801e83

stack72 commented 2026-06-08 13:00:35 +00:00

Author

Owner

Copy link

Code Review

Blocking Issues

None.

Observations

All 263 changed files are under model/ (auto-generated). Changes fall into two categories:

1. AWS _lib/aws.ts - 249 files, identical change each

Every file gets the same 5-line else-if branch adding a warning for partial credentials. All 249 files share identical before/after git object hashes (3365a615a to 52c72eafb), which is only possible via the codegen pipeline - not hand-editing.

Verified: codegen/aws/libGenerator.ts on origin/main already contains this exact code (merged via PR #41). This PR propagates a previously-landed template change to the generated output. Legitimate codegen regeneration even though codegen/ itself does not change in this PR.

The warning does not log any credential values - only a diagnostic message. No security concern.

2. GCP containeranalysis and dataplex - schema + version changes

• containeranalysis: removes cvssV4 fields from notes.ts, notes_occurrences.ts, occurrences.ts; version bump 2026.06.07.1 to 2026.06.08.1.
• dataplex: adds unstructuredDataProfileResult to datascans.ts and datascans_jobs.ts; version bump and manifest releaseNotes updated.

Both are clean upstream-schema regenerations consistent with the surrounding generated code style.

Suggestions

1. The commit message does not mention that the AWS _lib/aws.ts regeneration propagates the earlier libGenerator.ts template change (PR #41). A note in the PR body would make the audit trail clearer for future reviewers.

## Code Review ### Blocking Issues None. ### Observations All 263 changed files are under model/ (auto-generated). Changes fall into two categories: **1. AWS _lib/aws.ts - 249 files, identical change each** Every file gets the same 5-line else-if branch adding a warning for partial credentials. All 249 files share identical before/after git object hashes (3365a615a to 52c72eafb), which is only possible via the codegen pipeline - not hand-editing. Verified: `codegen/aws/libGenerator.ts` on `origin/main` already contains this exact code (merged via PR #41). This PR propagates a previously-landed template change to the generated output. Legitimate codegen regeneration even though `codegen/` itself does not change in this PR. The warning does not log any credential values - only a diagnostic message. No security concern. **2. GCP containeranalysis and dataplex - schema + version changes** - containeranalysis: removes `cvssV4` fields from `notes.ts`, `notes_occurrences.ts`, `occurrences.ts`; version bump 2026.06.07.1 to 2026.06.08.1. - dataplex: adds `unstructuredDataProfileResult` to `datascans.ts` and `datascans_jobs.ts`; version bump and manifest `releaseNotes` updated. Both are clean upstream-schema regenerations consistent with the surrounding generated code style. ### Suggestions 1. The commit message does not mention that the AWS `_lib/aws.ts` regeneration propagates the earlier `libGenerator.ts` template change (PR #41). A note in the PR body would make the audit trail clearer for future reviewers.

stack72 merged commit a98def6d3a into main 2026-06-08 16:13:09 +00:00

stack72 deleted branch automated/regenerate-models 2026-06-08 16:13:10 +00:00

stack72 referenced this pull request from a commit 2026-06-08 16:13:10 +00:00

chore: regenerate models from upstream schemas (#44)

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

chore: regenerate models from upstream schemas #51

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

No description provided.