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 github.com/hashicorp/vault/sdk from 0.1.13 to 0.2.0 #14

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Apr 1, 2021

Bumps github.com/hashicorp/vault/sdk from 0.1.13 to 0.2.0.

Changelog

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

0.2.0 (July 13, 2015)

FEATURES:

  • Key Rotation Support: The rotate command can be used to rotate the master encryption key used to write data to the storage (physical) backend. GH-277
  • Rekey Support: Rekey can be used to rotate the master key and change the configuration of the unseal keys (number of shares, threshold required). GH-277
  • New secret backend: pki: Enable Vault to be a certificate authority and generate signed TLS certificates. GH-310
  • New secret backend: cassandra: Generate dynamic credentials for Cassandra GH-363
  • New storage backend: etcd: store physical data in etcd GH-259 GH-297
  • New storage backend: s3: store physical data in S3. Does not support HA. GH-242
  • New storage backend: MySQL: store physical data in MySQL. Does not support HA. GH-324
  • transit secret backend supports derived keys for per-transaction unique keys GH-399

IMPROVEMENTS:

  • cli/auth: Enable cert method GH-380
  • cli/auth: read input from stdin GH-250
  • cli/read: Ability to read a single field from a secret GH-257
  • cli/write: Adding a force flag when no input required
  • core: allow time duration format in place of seconds for some inputs
  • core: audit log provides more useful information GH-360
  • core: graceful shutdown for faster HA failover
  • core: change policy format to use explicit globbing GH-400 Any existing policy in Vault is automatically upgraded to avoid issues. All policy files must be updated for future writes. Adding the explicit glob character * to the path specification is all that is required.
  • core: policy merging to give deny highest precedence GH-400
  • credential/app-id: Protect against timing attack on app-id
  • credential/cert: Record the common name in the metadata GH-342
  • credential/ldap: Allow TLS verification to be disabled GH-372
  • credential/ldap: More flexible names allowed GH-245 GH-379 GH-367
  • credential/userpass: Protect against timing attack on password
  • credential/userpass: Use bcrypt for password matching
  • http: response codes improved to reflect error GH-366
  • http: the sys/health endpoint supports ?standbyok to return 200 on standby GH-389
  • secret/app-id: Support deleting AppID and UserIDs GH-200
  • secret/consul: Fine grained lease control GH-261
  • secret/transit: Decouple raw key from key management endpoint GH-355
  • secret/transit: Upsert named key when encrypt is used GH-355

... (truncated)

Commits
  • 358a3c2 Cutting v0.2.0
  • 5d0f55c CHANGELOG updates
  • fce7c43 physical/zk: Fixing node representation. Fixes #416
  • 3d216c3 api: fixing 404 handling of GetPolicy
  • 0cc974b website: fixing documentation errors. Fixes #412
  • f253439 physical/zk: remove recursive delete behavior, still broken
  • 10f23df website: update HA status, discourage ZK
  • 4c4dc45 physical: ensure backend does NOT do recursive delete
  • bff57f8 vault: guard against potentially missing keyring
  • c9e8ca8 CHANGELOG updates
  • 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)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Apr 1, 2021
@dependabot dependabot bot force-pushed the dependabot/go_modules/github.com/hashicorp/vault/sdk-0.2.0 branch from ac9f952 to 70365ee Compare May 12, 2021 13:32
@dependabot dependabot bot force-pushed the dependabot/go_modules/github.com/hashicorp/vault/sdk-0.2.0 branch from 70365ee to 2fad89a Compare May 12, 2021 13:34
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Jul 14, 2021

A newer version of github.com/hashicorp/vault/sdk exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

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 go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant