Bump boto3 from 1.18.11 to 1.18.17

[dependabot]

Bumps boto3 from 1.18.11 to 1.18.17.

Changelog

Sourced from boto3's changelog.

1.18.17

• api-change:wafv2: [botocore] This release adds APIs to support versioning feature of AWS WAF Managed rule groups
• api-change:rekognition: [botocore] This release adds support for four new types of segments (opening credits, content segments, slates, and studio logos), improved accuracy for credits and shot detection and new filters to control black frame detection.
• api-change:ssm: [botocore] Documentation updates for AWS Systems Manager.

1.18.16

• api-change:synthetics: [botocore] Documentation updates for Visual Monitoring feature and other doc ticket fixes.
• api-change:chime-sdk-identity: [botocore] The Amazon Chime SDK Identity APIs allow software developers to create and manage unique instances of their messaging applications.
• api-change:chime-sdk-messaging: [botocore] The Amazon Chime SDK Messaging APIs allow software developers to send and receive messages in custom messaging applications.
• api-change:connect: [botocore] This release adds support for agent status and hours of operation. For details, see the Release Notes in the Amazon Connect Administrator Guide.
• api-change:lightsail: [botocore] This release adds support to track when a bucket access key was last used.
• api-change:athena: [botocore] Documentation updates for Athena.

1.18.15

• api-change:lexv2-models: [botocore] Update lexv2-models client to latest version
• api-change:autoscaling: [botocore] EC2 Auto Scaling adds configuration checks and Launch Template validation to Instance Refresh.

1.18.14

• api-change:rds: [botocore] This release adds AutomaticRestartTime to the DescribeDBInstances and DescribeDBClusters operations. AutomaticRestartTime indicates the time when a stopped DB instance or DB cluster is restarted automatically.
• api-change:imagebuilder: [botocore] Updated list actions to include a list of valid filters that can be used in the request.
• api-change:transcribe: [botocore] This release adds support for call analytics (batch) within Amazon Transcribe.
• api-change:events: [botocore] Update events client to latest version
• api-change:ssm-incidents: [botocore] Documentation updates for Incident Manager.

1.18.13

• api-change:redshift: [botocore] API support for Redshift Data Sharing feature.
• api-change:iotsitewise: [botocore] My AWS Service (placeholder) - This release introduces custom Intervals and offset for tumbling window in metric for AWS IoT SiteWise.
• api-change:glue: [botocore] Add ConcurrentModificationException to create-table, delete-table, create-database, update-database, delete-database
• api-change:mediaconvert: [botocore] AWS Elemental MediaConvert SDK has added control over the passthrough of XDS captions metadata to outputs.
• api-change:proton: [botocore] Docs only add idempotent create apis

1.18.12

• api-change:ssm-contacts: [botocore] Added new attribute in AcceptCode API. AcceptCodeValidation takes in two values - ENFORCE, IGNORE. ENFORCE forces validation of accept code and IGNORE ignores it which is also the default behavior; Corrected TagKeyList length from 200 to 50

... (truncated)

Commits

• ea7bed7 Merge branch 'release-1.18.17'
• 616426f Bumping version to 1.18.17
• 8d8e689 Add changelog entries from botocore
• 2634e76 Merge branch 'release-1.18.16'
• ddedebd Merge branch 'release-1.18.16' into develop
• d401cb0 Bumping version to 1.18.16
• dbb9322 Add changelog entries from botocore
• 0b26529 Merge branch 'release-1.18.15'
• 33d41ed Merge branch 'release-1.18.15' into develop
• afad98b Bumping version to 1.18.15
• 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)

[dependabot]

The following labels could not be found: python.

[openshift-ci]

[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]

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.