Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump boto3 from 1.17.23 to 1.17.33 #626

Merged
merged 1 commit into from
Mar 22, 2021

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 22, 2021

Bumps boto3 from 1.17.23 to 1.17.33.

Changelog

Sourced from boto3's changelog.

1.17.33

  • api-change:sagemaker: [botocore] Adding authentication support for pulling images stored in private Docker registries to build containers for real-time inference.
  • api-change:ec2: [botocore] X2gd instances are the next generation of memory-optimized instances powered by AWS-designed, Arm-based AWS Graviton2 processors.

1.17.32

  • bugfix:s3: [botocore] Updated mislabeled exceptions for S3 Object Lambda

1.17.31

  • api-change:autoscaling: [botocore] Amazon EC2 Auto Scaling Instance Refresh now supports phased deployments.
  • api-change:s3: [botocore] S3 Object Lambda is a new S3 feature that enables users to apply their own custom code to process the output of a standard S3 GET request by automatically invoking a Lambda function with a GET request
  • api-change:redshift: [botocore] Add new fields for additional information about VPC endpoint for clusters with reallocation enabled, and a new field for total storage capacity for all clusters.
  • api-change:s3control: [botocore] S3 Object Lambda is a new S3 feature that enables users to apply their own custom code to process the output of a standard S3 GET request by automatically invoking a Lambda function with a GET request
  • api-change:securityhub: [botocore] New object for separate provider and customer values. New objects track S3 Public Access Block configuration and identify sensitive data. BatchImportFinding requests are limited to 100 findings.

1.17.30

  • api-change:sagemaker: [botocore] Support new target device ml_eia2 in SageMaker CreateCompilationJob API
  • api-change:batch: [botocore] Making serviceRole an optional parameter when creating a compute environment. If serviceRole is not provided then Service Linked Role will be created (or reused if it already exists).

1.17.29

  • api-change:lambda: [botocore] Allow empty list for function response types
  • api-change:iam: [botocore] Documentation updates for AWS Identity and Access Management (IAM).
  • api-change:mediaconnect: [botocore] This release adds support for the SRT-listener protocol on sources and outputs.
  • api-change:accessanalyzer: [botocore] This release adds support for the ValidatePolicy API. IAM Access Analyzer is adding over 100 policy checks and actionable recommendations that help you validate your policies during authoring.
  • api-change:mediatailor: [botocore] MediaTailor channel assembly is a new manifest-only service that allows you to assemble linear streams using your existing VOD content.
  • api-change:mwaa: [botocore] This release adds UPDATE_FAILED and UNAVAILABLE MWAA environment states.
  • api-change:gamelift: [botocore] GameLift expands to six new AWS Regions, adds support for multi-location fleets to streamline management of hosting resources, and lets you customize more of the game session placement process.

1.17.28

  • api-change:fis: [botocore] Initial release of AWS Fault Injection Simulator, a managed service that enables you to perform fault injection experiments on your AWS workloads
  • api-change:codedeploy: [botocore] AWS CodeDeploy can now detect instances running an outdated revision of your application and automatically update them with the latest revision.
  • api-change:emr: [botocore] Update emr client to latest version
  • api-change:ecs: [botocore] This is for ecs exec feature release which includes two new APIs - execute-command and update-cluster and an AWS CLI customization for execute-command API

... (truncated)

Commits
  • 62438ac Merge branch 'release-1.17.33'
  • da6a1f0 Bumping version to 1.17.33
  • a057735 Add changelog entries from botocore
  • cf381af Merge branch 'release-1.17.32'
  • b4ffe7a Merge branch 'release-1.17.32' into develop
  • 0851a2c Bumping version to 1.17.32
  • a3a25e6 Add changelog entries from botocore
  • 95daadf Merge branch 'release-1.17.31'
  • d27ddcf Merge branch 'release-1.17.31' into develop
  • 272741a Bumping version to 1.17.31
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [boto3](https://github.com/boto/boto3) from 1.17.23 to 1.17.33.
- [Release notes](https://github.com/boto/boto3/releases)
- [Changelog](https://github.com/boto/boto3/blob/develop/CHANGELOG.rst)
- [Commits](boto/boto3@1.17.23...1.17.33)

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. labels Mar 22, 2021
@dependabot dependabot bot requested review from romfreiman and ronniel1 March 22, 2021 06:02
@openshift-ci-robot
Copy link

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

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

1 similar comment
@openshift-ci-robot
Copy link

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

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
Copy link

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.

@openshift-ci-robot openshift-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Mar 22, 2021
@openshift-ci
Copy link

openshift-ci bot commented Mar 22, 2021

@dependabot[bot]: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/unit 81f0cbe link /test unit

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit d6e5cda into master Mar 22, 2021
@openshift-merge-robot openshift-merge-robot deleted the dependabot/pip/boto3-1.17.33 branch March 22, 2021 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants