Bump boto3 from 1.26.28 to 1.26.32

[dependabot]

Bumps boto3 from 1.26.28 to 1.26.32.

Changelog

Sourced from boto3's changelog.

1.26.32

• enhancement:s3: s3.transfer methods accept path-like objects as input
• api-change:appflow: [botocore] This release updates the ListConnectorEntities API action so that it returns paginated responses that customers can retrieve with next tokens.
• api-change:cloudfront: [botocore] Updated documentation for CloudFront
• api-change:datasync: [botocore] AWS DataSync now supports the use of tags with task executions. With this new feature, you can apply tags each time you execute a task, giving you greater control and management over your task executions.
• api-change:efs: [botocore] Update efs client to latest version
• api-change:guardduty: [botocore] This release provides the valid characters for the Description and Name field.
• api-change:iotfleetwise: [botocore] Updated error handling for empty resource names in "UpdateSignalCatalog" and "GetModelManifest" operations.
• api-change:sagemaker: [botocore] AWS sagemaker - Features: This release adds support for random seed, it's an integer value used to initialize a pseudo-random number generator. Setting a random seed will allow the hyperparameter tuning search strategies to produce more consistent configurations for the same tuning job.

1.26.31

• api-change:backup-gateway: [botocore] This release adds support for VMware vSphere tags, enabling customer to protect VMware virtual machines using tag-based policies for AWS tags mapped from vSphere tags. This release also adds support for customer-accessible gateway-hypervisor interaction log and upload bandwidth rate limit schedule.
• api-change:connect: [botocore] Added support for "English - New Zealand" and "English - South African" to be used with Amazon Connect Custom Vocabulary APIs.
• api-change:ecs: [botocore] This release adds support for container port ranges in ECS, a new capability that allows customers to provide container port ranges to simplify use cases where multiple ports are in use in a container. This release updates TaskDefinition mutation APIs and the Task description APIs.
• api-change:eks: [botocore] Add support for Windows managed nodes groups.
• api-change:glue: [botocore] This release adds support for AWS Glue Crawler with native DeltaLake tables, allowing Crawlers to classify Delta Lake format tables and catalog them for query engines to query against.
• api-change:kinesis: [botocore] Added StreamARN parameter for Kinesis Data Streams APIs. Added a new opaque pagination token for ListStreams. SDKs will auto-generate Account Endpoint when accessing Kinesis Data Streams.
• api-change:location: [botocore] This release adds support for a new style, "VectorOpenDataStandardLight" which can be used with the new data source, "Open Data Maps (Preview)".
• api-change:m2: [botocore] Adds an optional create-only KmsKeyId property to Environment and Application resources.
• api-change:sagemaker: [botocore] SageMaker Inference Recommender now allows customers to load tests their models on various instance types using private VPC.
• api-change:securityhub: [botocore] Added new resource details objects to ASFF, including resources for AwsEc2LaunchTemplate, AwsSageMakerNotebookInstance, AwsWafv2WebAcl and AwsWafv2RuleGroup.
• api-change:translate: [botocore] Raised the input byte size limit of the Text field in the TranslateText API to 10000 bytes.

1.26.30

• api-change:ce: [botocore] This release supports percentage-based thresholds on Cost Anomaly Detection alert subscriptions.
• api-change:cloudwatch: [botocore] Update cloudwatch client to latest version
• api-change:networkmanager: [botocore] Appliance Mode support for AWS Cloud WAN.
• api-change:redshift-data: [botocore] This release adds a new --client-token field to ExecuteStatement and BatchExecuteStatement operations. Customers can now run queries with the additional client token parameter to ensures idempotency.
• api-change:sagemaker-metrics: [botocore] Update SageMaker Metrics documentation.

1.26.29

• api-change:cloudtrail: [botocore] Merging mainline branch for service model into mainline release branch. There are no new APIs.
• api-change:rds: [botocore] This deployment adds ClientPasswordAuthType field to the Auth structure of the DBProxy.

Commits

• 3041f18 Merge branch 'release-1.26.32'
• 6af157c Bumping version to 1.26.32
• a445626 Add changelog entries from botocore
• 3442539 S3 upload_file, download file to support path-lib objects (#2259)
• dc25471 Merge branch 'release-1.26.31'
• 3f5a1b3 Merge branch 'release-1.26.31' into develop
• aa0f99a Bumping version to 1.26.31
• 5051df9 Add changelog entries from botocore
• c5d8e4a Merge branch 'release-1.26.30'
• ed6b741 Merge branch 'release-1.26.30' into develop
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[codecov]

Codecov Report

Merging #10425 (8af958d) into master (d45c601) will increase coverage by 0.00%.
The diff coverage is n/a.

❗ Current head 8af958d differs from pull request most recent head 9e896dc. Consider uploading reports for the commit 9e896dc to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #10425   +/-   ##
=======================================
  Coverage   61.94%   61.95%           
=======================================
  Files         827      827           
  Lines       50900    50900           
  Branches     6551     6551           
=======================================
+ Hits        31532    31534    +2     
+ Misses      17686    17683    -3     
- Partials     1682     1683    +1     

[github-actions]

The backport to 4.1.x failed:

The process 'git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-4.1.x 4.1.x
# Navigate to the new working tree
cd .worktrees/backport-4.1.x
# Create a new branch
git switch --create backport-10425-to-4.1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick ce73fd333e62ad8758932435421eb27a7c07fcef
# Push it to GitHub
git push --set-upstream origin backport-10425-to-4.1.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-4.1.x

Then, create a pull request where the base branch is 4.1.x and the compare/head branch is backport-10425-to-4.1.x.

[github-actions]

The backport to 4.1.x failed:

The process 'git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-4.1.x 4.1.x
# Navigate to the new working tree
cd .worktrees/backport-4.1.x
# Create a new branch
git switch --create backport-10425-to-4.1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick ce73fd333e62ad8758932435421eb27a7c07fcef
# Push it to GitHub
git push --set-upstream origin backport-10425-to-4.1.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-4.1.x

Then, create a pull request where the base branch is 4.1.x and the compare/head branch is backport-10425-to-4.1.x.