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

build(deps): bump github.com/aws/aws-sdk-go from 1.25.41 to 1.42.30 #120

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Jan 10, 2022

Bumps github.com/aws/aws-sdk-go from 1.25.41 to 1.42.30.

Release notes

Sourced from github.com/aws/aws-sdk-go's releases.

Release v1.42.30 (2022-01-07)

Service Client Updates

  • service/medialive: Updates service API and documentation
    • This release adds support for selecting the Program Date Time (PDT) Clock source algorithm for HLS outputs.

Release v1.42.29 (2022-01-06)

Service Client Updates

  • service/appsync: Updates service API and documentation
  • service/ec2: Updates service API and documentation
    • This release introduces On-Demand Capacity Reservation support for Cluster Placement Groups, adds Tags on instance Metadata, and includes documentation updates for Amazon EC2.
  • service/es: Updates service API and documentation
    • Amazon OpenSearch Service adds support for Fine Grained Access Control for existing domains running Elasticsearch version 6.7 and above
  • service/iotwireless: Updates service API, documentation, and paginators
  • service/mediatailor: Updates service API and documentation
  • service/mwaa: Updates service API and documentation
  • service/opensearch: Updates service API and documentation

Release v1.42.28 (2022-01-05)

Service Client Updates

  • service/appstream: Updates service API and documentation
    • Includes APIs for App Entitlement management regarding entitlement and entitled application association.
  • service/cloudtrail: Updates service API, documentation, and paginators
    • This release adds support for CloudTrail Lake, a new feature that lets you run SQL-based queries on events that you have aggregated into event data stores. New APIs have been added for creating and managing event data stores, and creating, running, and managing queries in CloudTrail Lake.
  • service/ec2: Updates service API and documentation
    • This release adds a new API called ModifyVpcEndpointServicePayerResponsibility which allows VPC endpoint service owners to take payer responsibility of their VPC Endpoint connections.
  • service/ecs: Updates service documentation
    • Documentation update for ticket fixes.
  • service/eks: Updates service API and documentation
  • service/glue: Updates service API, documentation, and paginators
    • Add Delta Lake target support for Glue Crawler and 3rd Party Support for Lake Formation
  • service/iot: Updates service API and documentation
    • This release adds an automatic retry mechanism for AWS IoT Jobs. You can now define a maximum number of retries for each Job rollout, along with the criteria to trigger the retry for FAILED/TIMED_OUT/ALL(both FAILED an TIMED_OUT) job.
  • service/lakeformation: Updates service API and documentation
  • service/quicksight: Updates service documentation
    • Multiple Doc-only updates for Amazon QuickSight.
  • service/sagemaker: Updates service API
    • Amazon SageMaker now supports running training jobs on ml.g5 instance types.
  • service/snowball: Updates service API, documentation, and examples
    • Updating validation rules for interfaces used in the Snowball API to tighten security of service.

Release v1.42.27 (2022-01-04)

Service Client Updates

... (truncated)

Changelog

Sourced from github.com/aws/aws-sdk-go's changelog.

Release v1.42.30 (2022-01-07)

Service Client Updates

  • service/medialive: Updates service API and documentation
    • This release adds support for selecting the Program Date Time (PDT) Clock source algorithm for HLS outputs.

Release v1.42.29 (2022-01-06)

Service Client Updates

  • service/appsync: Updates service API and documentation
  • service/ec2: Updates service API and documentation
    • This release introduces On-Demand Capacity Reservation support for Cluster Placement Groups, adds Tags on instance Metadata, and includes documentation updates for Amazon EC2.
  • service/es: Updates service API and documentation
    • Amazon OpenSearch Service adds support for Fine Grained Access Control for existing domains running Elasticsearch version 6.7 and above
  • service/iotwireless: Updates service API, documentation, and paginators
  • service/mediatailor: Updates service API and documentation
  • service/mwaa: Updates service API and documentation
  • service/opensearch: Updates service API and documentation

Release v1.42.28 (2022-01-05)

Service Client Updates

  • service/appstream: Updates service API and documentation
    • Includes APIs for App Entitlement management regarding entitlement and entitled application association.
  • service/cloudtrail: Updates service API, documentation, and paginators
    • This release adds support for CloudTrail Lake, a new feature that lets you run SQL-based queries on events that you have aggregated into event data stores. New APIs have been added for creating and managing event data stores, and creating, running, and managing queries in CloudTrail Lake.
  • service/ec2: Updates service API and documentation
    • This release adds a new API called ModifyVpcEndpointServicePayerResponsibility which allows VPC endpoint service owners to take payer responsibility of their VPC Endpoint connections.
  • service/ecs: Updates service documentation
    • Documentation update for ticket fixes.
  • service/eks: Updates service API and documentation
  • service/glue: Updates service API, documentation, and paginators
    • Add Delta Lake target support for Glue Crawler and 3rd Party Support for Lake Formation
  • service/iot: Updates service API and documentation
    • This release adds an automatic retry mechanism for AWS IoT Jobs. You can now define a maximum number of retries for each Job rollout, along with the criteria to trigger the retry for FAILED/TIMED_OUT/ALL(both FAILED an TIMED_OUT) job.
  • service/lakeformation: Updates service API and documentation
  • service/quicksight: Updates service documentation
    • Multiple Doc-only updates for Amazon QuickSight.
  • service/sagemaker: Updates service API
    • Amazon SageMaker now supports running training jobs on ml.g5 instance types.
  • service/snowball: Updates service API, documentation, and examples
    • Updating validation rules for interfaces used in the Snowball API to tighten security of service.

Release v1.42.27 (2022-01-04)

Service Client Updates

... (truncated)

Commits

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 [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go) from 1.25.41 to 1.42.30.
- [Release notes](https://github.com/aws/aws-sdk-go/releases)
- [Changelog](https://github.com/aws/aws-sdk-go/blob/main/CHANGELOG.md)
- [Commits](aws/aws-sdk-go@v1.25.41...v1.42.30)

---
updated-dependencies:
- dependency-name: github.com/aws/aws-sdk-go
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Jan 10, 2022
@pull-request-quantifier-deprecated

This PR has 21 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Extra Small
Size       : +14 -7
Percentile : 8.4%

Total files changed: 2

Change summary by file extension:
.mod : +3 -3
.sum : +11 -4

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detetcted.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Jan 11, 2022

Superseded by #122.

@dependabot dependabot bot closed this Jan 11, 2022
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/aws/aws-sdk-go-1.42.30 branch January 11, 2022 07:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file Extra Small go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants