search

msrose / slack-name-battle

:collision: Engage in the sacred Name Battle... on Slack!
MIT License
3 stars 0 forks source link

chore: bump aws-sdk from 2.686.0 to 2.729.0 in /name-battle #78

Closed dependabot-preview[bot] closed 4 years ago

dependabot-preview[bot] commented 4 years ago

Bumps aws-sdk from 2.686.0 to 2.729.0.

Release notes

Sourced from aws-sdk's releases.

Release v2.729.0

See changelog for more information.

Release v2.728.0

See changelog for more information.

Release v2.727.1

See changelog for more information.

Release v2.727.0

See changelog for more information.

Release v2.726.0

See changelog for more information.

Release v2.725.0

See changelog for more information.

Release v2.724.0

See changelog for more information.

Release v2.723.0

See changelog for more information.

Release v2.722.0

See changelog for more information.

Release v2.721.0

See changelog for more information.

Release v2.720.0

See changelog for more information.

Release v2.719.0

See changelog for more information.

Release v2.718.0

See changelog for more information.

Release v2.717.0

See changelog for more information.

Release v2.716.0

See changelog for more information.

Release v2.715.0

See changelog for more information.

Release v2.714.2

See changelog for more information.

Changelog

Sourced from aws-sdk's changelog.

2.729.0

  • feature: Glue: AWS Glue now adds support for Network connection type enabling you to access resources inside your VPC using Glue crawlers and Glue ETL jobs.
  • feature: Organizations: Documentation updates for some new error reasons.
  • feature: S3: Updates Amazon S3 API reference documentation.
  • feature: SMS: In this release, AWS Server Migration Service (SMS) has added new features: 1. APIs to work with application and instance level validation 2. Import application catalog from AWS Application Discovery Service 3. For an application you can start on-demand replication

2.728.0

  • feature: EC2: This release supports Wavelength resources, including carrier gateways, and carrier IP addresses.
  • feature: LexModelBuildingService: Amazon Lex supports the option to enable accuracy improvements and specify an intent classification confidence score threshold.
  • feature: LexRuntime: Amazon Lex supports intent classification confidence scores along with a list of the top five intents.
  • feature: Personalize: Add 'exploration' functionality
  • feature: PersonalizeEvents: Adds support implicit and explicit impression input
  • feature: PersonalizeRuntime: Adds support for implicit impressions

2.727.1

  • bugfix: docs: Add awsdocs-legal-zone-copyright div

2.727.0

  • feature: AppSync: AWS AppSync releases support for Direct Lambda Resolvers.
  • feature: TranscribeService: Amazon Transcribe now supports custom language models, which can improve transcription accuracy for your specific use case.

2.726.0

  • feature: SSM: Adds a waiter for CommandExecuted and paginators for various other APIs.

2.725.0

  • feature: Chime: This release increases the CreateMeetingWithAttendee max attendee limit to 10.
  • feature: PersonalizeRuntime: Adds support to use filters with Personalized Ranking recipe
  • feature: StorageGateway: Add support for gateway VM deprecation dates
  • feature: WAFV2: Add ManagedByFirewallManager flag to the logging configuration, which indicates whether AWS Firewall Manager controls the configuration.

2.724.0

  • feature: CodeBuild: Adding support for BuildBatch, and CodeCoverage APIs. BuildBatch allows you to model your project environment in source, and helps start multiple builds with a single API call. CodeCoverage allows you to track your code coverage using AWS CodeBuild.
  • feature: EC2: EC2 On-Demand Capacity Reservations now adds support to bring your own licenses (BYOL) of Windows operating system to launch EC2 instances.
  • feature: GuardDuty: GuardDuty can now provide detailed cost metrics broken down by account, data source, and S3 resources, based on the past 30 days of usage. This new feature also supports viewing cost metrics for all member accounts as a GuardDuty master.
  • feature: Kafka: Amazon MSK has added a new API that allows you to reboot brokers within a cluster.
  • feature: SESV2: This release makes more API operations available to customers in version 2 of the Amazon SES API. With these additions, customers can now access sending authorization, custom verification email, and template API operations. With this release, Amazon SES is also providing new and updated APIs to allow customers to request production access.
  • feature: ServiceCatalog: This release adds support for ProvisionProduct, UpdateProvisionedProduct & DescribeProvisioningParameters by product name, provisioning artifact name and path name. In addition DescribeProvisioningParameters now returns a list of provisioning artifact outputs.

2.723.0

  • feature: EC2: Adding support to target EC2 On-Demand Capacity Reservations within an AWS Resource Group to launch EC2 instances.
  • feature: ECR: This release adds support for encrypting the contents of your Amazon ECR repository with customer master keys (CMKs) stored in AWS Key Management Service.
  • feature: Firehose: This release includes a new Kinesis Data Firehose feature that supports data delivery to Https endpoint and to partners. You can now use Kinesis Data Firehose to ingest real-time data and deliver to Https endpoint and partners in a serverless, reliable, and salable manner.
  • feature: GuardDuty: GuardDuty now supports S3 Data Events as a configurable data source type. This feature expands GuardDuty's monitoring scope to include S3 data plane operations, such as GetObject and PutObject. This data source is optional and can be enabled or disabled at anytime. Accounts already using GuardDuty must first enable the new feature to use it; new accounts will be enabled by default. GuardDuty masters can configure this data source for individual member accounts and GuardDuty masters associated through AWS Organizations can automatically enable the data source in member accounts.
  • feature: ResourceGroups: Resource Groups released a new feature that enables you to create a group with an associated configuration that specifies how other AWS services interact with the group. There are two new operations GroupResources and UngroupResources to work on a group with a configuration. In this release, you can associate EC2 Capacity Reservations with a resource group. Resource Groups also added a new request parameter Group to replace GroupName for all existing operations.
  • feature: ServiceDiscovery: Added new attribute AWS_EC2_INSTANCE_ID for RegisterInstance API

2.722.0

  • feature: AutoScaling: Now you can enable Instance Metadata Service Version 2 (IMDSv2) or disable the instance metadata endpoint with Launch Configurations.
  • feature: EC2: Introduces support for tag-on-create capability for the following APIs: CreateVpnConnection, CreateVpnGateway, and CreateCustomerGateway. A user can now add tags while creating these resources. For further detail, please see AWS Tagging Strategies.
  • feature: IVS: Added a new error code, PendingVerification, to differentiate between errors caused by insufficient IAM permissions and errors caused by account verification.
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.

If all status checks pass Dependabot will automatically merge this pull request.

Note: This repo was added to Dependabot recently, so you'll receive a maximum of 1 PRs for your first few update runs. Once an update run creates fewer than 1 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.

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 badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in the `.dependabot/config.yml` file in this repo: - Update frequency - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)
codecov-commenter commented 4 years ago

Codecov Report

Merging #78 into master will not change coverage. The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #78   +/-   ##
=======================================
  Coverage   83.70%   83.70%           
=======================================
  Files           8        8           
  Lines         227      227           
  Branches       47       47           
=======================================
  Hits          190      190           
  Misses         36       36           
  Partials        1        1
dependabot-preview[bot] commented 4 years ago

Superseded by #80.