chore: regenerate models from upstream schemas #55
Loading…
Reference in a new issue
No description provided.
Delete branch "automated/regenerate-models"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Automated regeneration of extension models from upstream provider schemas.
Schema Sources
Review Notes
model/are auto-generated — review themanifest.yamldiffs for version changesCode Review
Blocking Issues
None.
Summary
All 51 changed files are under
model/— nocodegen/files were modified. This matches the established automated "chore: regenerate models from upstream schemas" CI workflow seen in PRs #47, #48, #51, and #52 (all merged to main), so the absence ofcodegen/changes is expected and not a sign of hand-editing.Every modified file retains its
// Auto-generated extension modelheader and// Do not edit manually. Re-generate with: deno task generate:awscomment, confirming these are codegen outputs, not hand-edits. CLAUDE.md's "Never hand-edit files undermodel/" rule is not violated.Change summary across providers:
log_alarm): RemovesQueryLanguagefield fromScheduledQueryConfiguration— upstream schema dropped it.dictionary): New model forAWS::ElementalInference::Dictionary.capacity_provider): Minor field update.global_cluster): New model forAWS::Neptune::GlobalCluster.organization_centralization_rule): Minor field update.user_journey): Minor field update.domain): Minor field update.association): AddsAssociationDispatchAssumeRoleandTagsfields reflecting upstream CloudFormation schema additions.enterprises,enterprises_enrollmenttokens): Field additions from upstream Discovery Document changes.connections): Addsparametersmap to bothauthenticationand connectorconfigurationblocks — upstream API additions.databases_documents): Minor update.accounts_datasources): Minor update.goldengateConnectionTypes,goldengateDeploymentEnvironments,goldengateDeploymentTypes,goldengateDeploymentVersionsfromreadResource(GET) toreadViaList(list-then-filter) — matches upstream API capability changes; adds new fields tocloudexadatainfrastructures,cloudvmclusters,exascaledbstoragevaults.privateclouds): Field additions.All version bumps follow CalVer (
2026.06.16.1) and include the requiredupgradeschain entry. Manifests are consistent with their model lists.Suggestions
bigqueryconnection/connections.tsGlobalArgsSchema usesz.unknown()for the nestedsecretValue.plaintextfield (insideauthentication.parameters), while the top-levelconfiguration.parametersusesz.string(). This asymmetry is likely a generated artifact from the upstream Discovery Document describing the field differently in nested vs. top-level contexts. Worth keeping an eye on whether the upstream schema stabilises, but not a blocker for a generated file.