Bump boto3 from 1.17.39 to 1.17.44

[dependabot]

Bumps boto3 from 1.17.39 to 1.17.44.

Changelog

Sourced from boto3's changelog.

1.17.44

• api-change:mediapackage: [botocore] SPEKE v2 is an upgrade to the existing SPEKE API to support multiple encryption keys, based on an encryption contract selected by the customer.
• api-change:imagebuilder: [botocore] This release adds support for Block Device Mappings for container image builds, and adds distribution configuration support for EC2 launch templates in AMI builds.

1.17.43

• api-change:route53resolver: [botocore] Route 53 Resolver DNS Firewall is a firewall service that allows you to filter and regulate outbound DNS traffic for your VPCs.
• api-change:mediaconvert: [botocore] MediaConvert now supports HLS ingest, sidecar WebVTT ingest, Teletext color & style passthrough to TTML subtitles, TTML to WebVTT subtitle conversion with style, & DRC profiles in AC3 audio.
• api-change:lightsail: [botocore] - This release adds support for state detail for Amazon Lightsail container services.
• api-change:kendra: [botocore] AWS Kendra's ServiceNow data source now supports OAuth 2.0 authentication and knowledge article filtering via a ServiceNow query.
• api-change:lex-models: [botocore] Lex now supports the ja-JP locale
• api-change:lex-runtime: [botocore] Update lex-runtime client to latest version
• api-change:fms: [botocore] Added Firewall Manager policy support for AWS Route 53 Resolver DNS Firewall.
• api-change:ec2: [botocore] VPC Flow Logs Service adds a new API, GetFlowLogsIntegrationTemplate, which generates CloudFormation templates for Athena. For more info, see https://docs.aws.amazon.com/console/vpc/flow-logs/athena
• api-change:wafv2: [botocore] Added support for ScopeDownStatement for ManagedRuleGroups, Labels, LabelMatchStatement, and LoggingFilter. For more information on these features, see the AWS WAF Developer Guide.

1.17.42

• api-change:iot: [botocore] Added ability to prefix search on attribute value for ListThings API.
• api-change:pricing: [botocore] Minor documentation and link updates.
• api-change:transcribe: [botocore] Amazon Transcribe now supports creating custom language models in the following languages: British English (en-GB), Australian English (en-AU), Indian Hindi (hi-IN), and US Spanish (es-US).
• api-change:cloudhsm: [botocore] Minor documentation and link updates.
• api-change:comprehend: [botocore] Support for customer managed KMS encryption of Comprehend custom models
• api-change:cognito-sync: [botocore] Minor documentation updates and link updates.
• api-change:batch: [botocore] AWS Batch adds support for Amazon EFS File System
• api-change:detective: [botocore] Added the ability to assign tag values to Detective behavior graphs. Tag values can be used for attribute-based access control, and for cost allocation for billing.
• api-change:iotwireless: [botocore] Add Sidewalk support to APIs: GetWirelessDevice, ListWirelessDevices, GetWirelessDeviceStatistics. Add Gateway connection status in GetWirelessGatewayStatistics API.
• api-change:cloudformation: [botocore] 1. Added a new parameter RegionConcurrencyType in OperationPreferences. 2. Changed the name of AccountUrl to AccountsUrl in DeploymentTargets parameter.
• api-change:cloud9: [botocore] Add ImageId input parameter to CreateEnvironmentEC2 endpoint. New parameter enables creation of environments with different AMIs.
• api-change:directconnect: [botocore] This release adds MACsec support to AWS Direct Connect
• api-change:redshift: [botocore] Enable customers to share access to their Redshift clusters from other VPCs (including VPCs from other accounts).
• api-change:workmail: [botocore] This release adds support for mobile device access rules management in Amazon WorkMail.
• api-change:datapipeline: [botocore] Minor documentation updates and link updates.
• api-change:machinelearning: [botocore] Minor documentation updates and link updates.

1.17.41

• api-change:sagemaker: [botocore] Amazon SageMaker Autopilot now supports 1) feature importance reports for AutoML jobs and 2) PartialFailures for AutoML jobs
• api-change:ec2-instance-connect: [botocore] Adding support to push SSH keys to the EC2 serial console in order to allow an SSH connection to your Amazon EC2 instance's serial port.
• api-change:cloudwatch: [botocore] Update cloudwatch client to latest version
• api-change:databrew: [botocore] This SDK release adds two new dataset features: 1) support for specifying a database connection as a dataset input 2) support for dynamic datasets that accept configurable parameters in S3 path.
• api-change:frauddetector: [botocore] This release adds support for Batch Predictions in Amazon Fraud Detector.

... (truncated)

Commits

• dd213cb Merge branch 'release-1.17.44'
• b18db36 Bumping version to 1.17.44
• d86a2c9 Add changelog entries from botocore
• a60637c Merge branch 'release-1.17.43' into develop
• ef72216 Merge branch 'release-1.17.43'
• 822c78e Bumping version to 1.17.43
• f91bcff Add changelog entries from botocore
• c05bf6e Merge branch 'release-1.17.42' into develop
• d5ffbd0 Merge branch 'release-1.17.42'
• 18735b0 Bumping version to 1.17.42
• 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)

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: dependabot[bot]

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: dependabot[bot]

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.