sensu-plugins / sensu-plugins-graphite

This plugin provides native Graphite instrumentation for monitoring, including: replication status, various Graphite data queries, mutators, and handlers
http://sensu-plugins.io
MIT License
22 stars 45 forks source link

Update rest-client requirement from = 1.8.0 to = 2.0.2 #72

Closed dependabot-preview[bot] closed 5 years ago

dependabot-preview[bot] commented 5 years ago

Updates the requirements on rest-client to permit the latest version.

Changelog *Sourced from [rest-client's changelog](https://github.com/rest-client/rest-client/blob/master/history.md).* > # 2.0.2 > > - Suppress the header override warning introduced in 2.0.1 if the value is the > same. There's no conflict if the value is unchanged. ([#578](https://github-redirect.dependabot.com/rest-client/rest-client/issues/578)) > > # 2.0.1 > > - Warn if auto-generated headers from the payload, such as Content-Type, > override headers set by the user. This is usually not what the user wants to > happen, and can be surprising. ([#554](https://github-redirect.dependabot.com/rest-client/rest-client/issues/554)) > - Drop the old check for weak default TLS ciphers, and use the built-in Ruby > defaults. Ruby versions from Oct. 2014 onward use sane defaults, so this is > no longer needed. ([#573](https://github-redirect.dependabot.com/rest-client/rest-client/issues/573)) > > # 2.0.0 > > This release is largely API compatible, but makes several breaking changes. > > - Drop support for Ruby 1.9 > - Allow mime-types as new as 3.x (requires ruby 2.0) > - Respect Content-Type charset header provided by server. Previously, > rest-client would not override the string encoding chosen by Net::HTTP. Now > responses that specify a charset will yield a body string in that encoding. > For example, `Content-Type: text/plain; charset=EUC-JP` will return a String > encoded with `Encoding::EUC_JP`. ([#361](https://github-redirect.dependabot.com/rest-client/rest-client/issues/361)) > - Change exceptions raised on request timeout. Instead of > `RestClient::RequestTimeout` (which is still used for HTTP 408), network > timeouts will now raise either `RestClient::Exceptions::ReadTimeout` or > `RestClient::Exceptions::OpenTimeout`, both of which inherit from > `RestClient::Exceptions::Timeout`. For backwards compatibility, this still > inherits from `RestClient::RequestTimeout` so existing uses will still work. > This may change in a future major release. These new timeout classes also > make the original wrapped exception available as `#original_exception`. > - Unify request exceptions under `RestClient::RequestFailed`, which still > inherits from `ExceptionWithResponse`. Previously, HTTP 304, 401, and 404 > inherited directly from `ExceptionWithResponse` rather than from > `RequestFailed`. Now _all_ HTTP status code exceptions inherit from both. > - Rename the `:timeout` request option to `:read_timeout`. When `:timeout` is > passed, now set both `:read_timeout` and `:open_timeout`. > - Change default HTTP Accept header to `*/*` > - Use a more descriptive User-Agent header by default > - Drop RC4-MD5 from default cipher list > - Only prepend http:// to URIs without a scheme > - Fix some support for using IPv6 addresses in URLs (still affected by Ruby > 2.0+ bug https://bugs.ruby-lang.org/issues/9129, with the fix expected to be > backported to 2.0 and 2.1) > - `Response` objects are now a subclass of `String` rather than a `String` that > mixes in the response functionality. Most of the methods remain unchanged, > but this makes it much easier to understand what is happening when you look > at a RestClient response object. There are a few additional changes: > ... (truncated)
Commits - See full diff in [compare view](https://github.com/rest-client/rest-client/commits/v2.0.2)


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.


Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 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 cancel merge` will cancel a previously requested merge - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major 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 use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@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 your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.
dependabot-preview[bot] commented 5 years ago

Superseded by #81.