build(deps): bump github.com/hashicorp/vault/sdk from 0.2.1 to 0.3.0

[dependabot]

Bumps github.com/hashicorp/vault/sdk from 0.2.1 to 0.3.0.

Changelog

Sourced from github.com/hashicorp/vault/sdk's changelog.

0.3.0 (September 28, 2015)

DEPRECATIONS/CHANGES:

Note: deprecations and breaking changes in upcoming releases are announced ahead of time on the "vault-tool" mailing list.

• Cookie Authentication Removed: As of 0.3 the only way to authenticate is via the X-Vault-Token header. Cookie authentication was hard to properly test, could result in browsers/tools/applications saving tokens in plaintext on disk, and other issues. GH-564
• Terminology/Field Names: Vault is transitioning from overloading the term "lease" to mean both "a set of metadata" and "the amount of time the metadata is valid". The latter is now being referred to as TTL (or "lease_duration" for backwards-compatibility); some parts of Vault have already switched to using "ttl" and others will follow in upcoming releases. In particular, the "token", "generic", and "pki" backends accept both "ttl" and "lease" but in 0.4 only "ttl" will be accepted. GH-528
• Downgrade Not Supported: Due to enhancements in the storage subsystem, values written by Vault 0.3+ will not be able to be read by prior versions of Vault. There are no expected upgrade issues, however, as with all critical infrastructure it is recommended to back up Vault's physical storage before upgrading.

FEATURES:

• SSH Backend: Vault can now be used to delegate SSH access to machines, via a (recommended) One-Time Password approach or by issuing dynamic keys. GH-385
• Cubbyhole Backend: This backend works similarly to the "generic" backend but provides a per-token workspace. This enables some additional authentication workflows (especially for containers) and can be useful to applications to e.g. store local credentials while being restarted or upgraded, rather than persisting to disk. GH-612
• Transit Backend Improvements: The transit backend now allows key rotation and datakey generation. For rotation, data encrypted with previous versions of the keys can still be decrypted, down to a (configurable) minimum previous version; there is a rewrap function for manual upgrades of ciphertext to newer versions. Additionally, the backend now allows generating and returning high-entropy keys of a configurable bitsize suitable for AES and other functions; this is returned wrapped by a named key, or optionally both wrapped and plaintext for immediate use. GH-626
• Global and Per-Mount Default/Max TTL Support: You can now set the default and maximum Time To Live for leases both globally and per-mount. Per-mount settings override global settings. Not all backends honor these settings yet, but the maximum is a hard limit enforced outside the backend. See the documentation for "/sys/mounts/" for details on configuring per-mount TTLs. GH-469
• PGP Encryption for Unseal Keys: When initializing or rotating Vault's master key, PGP/GPG public keys can now be provided. The output keys will be

... (truncated)

Commits

• 347f48c Cut version 0.3.0
• 23411f2 Format token lease/TTL as int in JSON API when looking up
• 07efc59 Update version number
• 102190f Update dist script
• 9f530d8 Merge pull request #647 from jszwedko/some-go-vet-changes
• 3868165 Fix warnings returned by make vet
• 70ce824 Switch per-mount values to strings going in and seconds coming out, like othe...
• ae8192f Merge pull request #643 from hashicorp/edit-this-page
• 493bf78 Add 'edit this page' link to footer
• 9018638 bundle update middleman-hashicorp
• 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)

[codecov-commenter]

Codecov Report

Merging #1552 (9b01c8d) into 3.0 (669ab0a) will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              3.0    #1552      +/-   ##
==========================================
- Coverage   41.75%   41.70%   -0.06%     
==========================================
  Files         258      258              
  Lines       15114    15114              
==========================================
- Hits         6311     6303       -8     
- Misses       8065     8070       +5     
- Partials      738      741       +3     

Impacted Files	Coverage Δ
filter/metrics/filter.go	85.00% <0.00%> (-15.00%)	⬇️
remoting/kubernetes/client.go	71.91% <0.00%> (-2.25%)	⬇️
metrics/prometheus/reporter.go	26.85% <0.00%> (-1.72%)	⬇️
remoting/kubernetes/listener.go	54.71% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 669ab0a...9b01c8d. Read the comment docs.