search

lrstanley / vault-unseal

auto-unseal utility for Hashicorp Vault
MIT License
238 stars 32 forks source link

Bump github.com/hashicorp/vault/api from 1.1.1 to 1.5.0 #11

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps github.com/hashicorp/vault/api from 1.1.1 to 1.5.0.

Changelog

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

1.5.0

July 21st, 2020

CHANGES:

  • audit: Token TTL and issue time are now provided in the auth portion of audit logs. [GH-9091]
  • auth/gcp: Changes the default name of the entity alias that gets created to be the role ID for both IAM and GCE authentication. [GH-99]
  • core: Remove the addition of newlines to parsed configuration when using integer/boolean values [GH-8928]
  • cubbyhole: Reject reads and writes to an empty ("") path. [GH-8971]
  • secrets/azure: Default password generation changed from uuid to cryptographically secure randomized string [GH-40]
  • storage/gcs: The credentials_file config option has been removed. The GOOGLE_APPLICATION_CREDENTIALS environment variable or default credentials may be used instead [GH-9424]
  • storage/raft: The storage configuration now accepts a new max_entry_size config that will limit the total size in bytes of any entry committed via raft. It defaults to "1048576" (1MiB). [GH-9027]
  • token: Token creation with custom token ID via id will no longer allow periods (.) as part of the input string. The final generated token value may contain periods, such as the s. prefix for service token indication. [GH-8646]
  • token: Token renewals will now return token policies within the token_policies , identity policies within identity_policies, and the full policy set within policies. [GH-8535]
  • go: Updated Go version to 1.14.4

FEATURES:

  • Monitoring: We have released a Splunk App [9] for Enterprise customers. The app is accompanied by an updated monitoring guide and a few new metrics to enable OSS users to effectively monitor Vault.
  • Password Policies: Allows operators to customize how passwords are generated for select secret engines (OpenLDAP, Active Directory, Azure, and RabbitMQ).
  • Replication UI Improvements: We have redesigned the replication UI to highlight the state and relationship between primaries and secondaries and improved management workflows, enabling a more holistic understanding of multiple Vault clusters.
  • Resource Quotas: As of 1.5, Vault supports specifying a quota to rate limit requests on OSS and Enterprise. Enterprise customers also have access to set quotas on the number of leases that can be generated on a path.
  • OpenShift Support: We have updated the Helm charts to allow users to install Vault onto their OpenShift clusters.
  • Seal Migration: We have made updates to allow migrations from auto unseal to Shamir unseal on Enterprise.
  • AWS Auth Web Identity Support: We've added support for AWS Web Identities, which will be used in the credentials chain if present.
  • Vault Monitor: Similar to the monitor command for Consul and Nomad, we have added the ability for Vault to stream logs from other Vault servers at varying log levels.
  • AWS Secrets Groups Support: IAM users generated by Vault may now be added to IAM Groups.
  • Integrated Storage as HA Storage: In Vault 1.5, it is possible to use Integrated Storage as HA Storage with a different storage backend as regular storage.
  • OIDC Auth Provider Extensions: We've added support to OIDC Auth to incorporate IdP-specific extensions. Currently this includes expanded Azure AD groups support.
  • GCP Secrets: Support BigQuery dataset ACLs in absence of IAM endpoints.
  • KMIP: Add support for signing client certificates requests (CSRs) rather than having them be generated entirely within Vault.

IMPROVEMENTS:

  • audit: Replication status requests are no longer audited. [GH-8877]
  • audit: Added mount_type field to requests and responses. [GH-9167]
  • auth/aws: Add support for Web Identity credentials [GH-7738]
  • auth/jwt: Support users that are members of more than 200 groups on Azure [GH-120]
  • auth/kerberos: Support identities without userPrincipalName [GH-44]
  • auth/kubernetes: Allow disabling iss validation [GH-91]
  • auth/kubernetes: Try reading the ca.crt and TokenReviewer JWT from the default service account [GH-83]
  • cli: Support reading TLS parameters from file for the vault operator raft join command. [GH-9060]
  • cli: Add a new subcommand, vault monitor, for tailing server logs in the console. [GH-8477]
  • core: Add the Go version used to build a Vault binary to the server message output. [GH-9078]
  • core: Added Password Policies for user-configurable password generation [GH-8637]
  • core: New telemetry metrics covering token counts, token creation, KV secret counts, lease creation. [GH-9239] [GH-9250] [GH-9244] [GH-9052]

... (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)
dependabot[bot] commented 2 years ago

Looks like github.com/hashicorp/vault/api is up-to-date now, so this is no longer needed.