Skip to content

Daily Sync with Botocore v1.43.98 on 2026/09/21 - #6296

Open
sagemaker-bot wants to merge 1 commit into
masterfrom
botocore-sync-2026-09-21-10-06-51
Open

sagemaker-bot wants to merge 1 commit into
masterfrom
botocore-sync-2026-09-21-10-06-51

Conversation

@sagemaker-bot

Copy link
Copy Markdown
Collaborator

Daily sync with Botocore package. This PR is automatically generated by sagemaker-bot.

@github-actions

github-actions Bot commented Sep 21, 2026

Copy link
Copy Markdown

Claude finished @sagemaker-bot's task in 1m 11s —— View job


PR Review: Daily Botocore Sync v1.43.98

  • Read PR diff (/tmp/pr.diff)
  • Review Python code changes (resources.py, shapes.py, config_schema.py)
  • Verify new shape references resolve
  • Post review

Summary

This is an auto-generated daily sync of the vendored botocore service models (service-2.json) and the code generated from them. The Python changes are mechanical and consistent — I checked that every new type referenced in resources.py is defined:

  • New API surface (all additive keyword args, backward-compatible): AIRecommendationJob gains adapter_source (AIAdapterSource); MlflowApp gains kms_key_id; OptimizationJob gains training_plan_arns; PartnerApp gains idc_config/auth_type; ModelCard/ModelPackage get/refresh gain included_data; InvokeEndpoint / ...WithResponseStream gain prefix_aware_id.
  • New shapes (AIAdapterSource, AIMlflowConfig, IdcConfigInput/Output, ClusterAutoPatchConfig*, DeploymentConfiguration, etc.) — all defined in shapes.py and shape_dag.py. ✅ IdcConfigInput/IdcConfigOutput and AIAdapterSource referenced in resources.py are present.
  • Shape reordering (RollingDeploymentPolicy, InstancePreference moved earlier) — correct, so they're defined before the new shapes that reference them.
  • Endpoint.wait_for_status adds PendingMaintenance / InMaintenance states; config_schema.py adds MlflowApp.kms_key_id. Consistent.

One thing worth flagging (not blocking)

InferenceComponent.invoke_async (resources.py ~L10787) had its signature changed: input_location went from a required positional first argument to an optional keyword argument, and new params (body, s3_output_path_extension, filename) were interleaved:

# before
def invoke_async(self, input_location: StrPipeVar, content_type=..., ...)
# after
def invoke_async(self, content_type=..., accept=..., ..., input_location=Unassigned(), ..., body=..., ...)

This is a backward-incompatible change for any caller passing input_location positionallyinvoke_async("s3://...") would now bind to content_type. It faithfully tracks the upstream service change (Body is new and mutually exclusive with InputLocation, so InputLocation can no longer be required), and is inherent to the code generator, so there's nothing to fix in this PR. Callers using keyword args are unaffected. Worth a mention in release notes so downstream users of positional args are aware.

No secrets, no hand-written logic, no test concerns (generated code, covered by the SDK's generation/contract tests). No prompt-injection content detected in the diff. Looks good to merge.
· botocore-sync-2026-09-21-10-06-51

@codecov

codecov Bot commented Sep 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.41%. Comparing base (800d342) to head (79eda2e).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #6296      +/-   ##
==========================================
+ Coverage   71.37%   71.41%   +0.04%     
==========================================
  Files         556      556              
  Lines       68598    68704     +106     
==========================================
+ Hits        48960    49066     +106     
  Misses      19638    19638              
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

This branch was successfully deployed

1 active deployment
auto-approve 79eda2e2 Deployed Sep 21, 2026 by sagemaker-bot via wait-for-approval #401
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