Bump boto3 from 1.17.33 to 1.17.39

[dependabot]

Bumps boto3 from 1.17.33 to 1.17.39.

Changelog

Sourced from boto3's changelog.

1.17.39

• api-change:iotwireless: [botocore] Support tag-on-create for WirelessDevice.
• api-change:customer-profiles: [botocore] This release adds an optional parameter named FlowDefinition in PutIntegrationRequest.
• api-change:events: [botocore] Add support for SageMaker Model Builder Pipelines Targets to EventBridge
• api-change:transcribe: [botocore] Amazon Transcribe now supports tagging words that match your vocabulary filter for batch transcription.

1.17.38

• api-change:lookoutmetrics: [botocore] Allowing uppercase alphabets for RDS and Redshift database names.

1.17.37

• api-change:sqs: [botocore] Documentation updates for Amazon SQS
• api-change:rekognition: [botocore] This release introduces AWS tagging support for Amazon Rekognition collections, stream processors, and Custom Label models.
• api-change:sagemaker: [botocore] This feature allows customer to specify the environment variables in their CreateTrainingJob requests.
• api-change:medialive: [botocore] EML now supports handling HDR10 and HLG 2020 color space from a Link input.
• api-change:lookoutmetrics: [botocore] Amazon Lookout for Metrics is now generally available. You can use Lookout for Metrics to monitor your data for anomalies. For more information, see the Amazon Lookout for Metrics Developer Guide.
• api-change:alexaforbusiness: [botocore] Added support for enabling and disabling data retention in the CreateProfile and UpdateProfile APIs and retrieving the state of data retention for a profile in the GetProfile API.

1.17.36

• api-change:ssm: [botocore] This release allows SSM Explorer customers to enable OpsData sources across their organization when creating a resource data sync.
• api-change:route53: [botocore] Documentation updates for route53
• bugfix:S3: [botocore] Fix an issue with XML newline normalization in PutBucketLifecycleConfiguration requests.
• api-change:s3: [botocore] Documentation updates for Amazon S3
• api-change:s3control: [botocore] Documentation updates for s3-control
• api-change:ec2: [botocore] maximumEfaInterfaces added to DescribeInstanceTypes API
• api-change:greengrass: [botocore] Updated the parameters to make name required for CreateGroup API.

1.17.35

• api-change:ce: [botocore] You can now create cost categories with inherited value rules and specify default values for any uncategorized costs.
• api-change:fis: [botocore] Updated maximum allowed size of action parameter from 64 to 1024
• api-change:redshift: [botocore] Removed APIs to control AQUA on clusters.
• api-change:iam: [botocore] Documentation updates for IAM operations and descriptions.
• api-change:gamelift: [botocore] GameLift adds support for using event notifications to monitor game session placements. Specify an SNS topic or use CloudWatch Events to track activity for a game session queue.

1.17.34

... (truncated)

Commits

• 8774b91 Merge branch 'release-1.17.39'
• 7fafee9 Bumping version to 1.17.39
• 92a2f9f Add changelog entries from botocore
• 3edfd0d Merge branch 'release-1.17.38'
• 1941bb3 Merge branch 'release-1.17.38' into develop
• 68b8585 Bumping version to 1.17.38
• fb2bf3b Add changelog entries from botocore
• 989ebbb Merge branch 'release-1.17.37'
• 95c414e Merge branch 'release-1.17.37' into develop
• 8cf6d7b Bumping version to 1.17.37
• 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.

[YuviGold]

/retest

[YuviGold]

/lgtm