This project is mirrored from https://gitee.com/NQL886/vault.git.
Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
- 09 Mar, 2021 1 commit
-
-
swayne275 authored
* update go version to 1.15.8 * add changelog * Revert "update go version to 1.15.8" This reverts commit e886f83b183199565bb9e742b43a6a896687b8ac. * just edit handcrafted files * results of make packages
-
- 08 Mar, 2021 3 commits
-
-
swayne275 authored
* update to 1.7.0 rc1 * go mod vendor
-
Vishal Nayak authored
-
Scott Miller authored
* Make sure we sanitize the rotation config on each clone * Add regression test for missing rotation config * use Equals * simplify Co-authored-by:
Scott G. Miller <smiller@hashicorp.com> Co-authored-by:
Brian Kassouf <briankassouf@users.noreply.github.com>
-
- 07 Mar, 2021 1 commit
-
-
Vishal Nayak authored
-
- 05 Mar, 2021 1 commit
-
-
Calvin Leung Huang authored
* mod: update plugin versions for 1.7.0 * command/agent: fix TestCFEndToEnd test
-
- 04 Mar, 2021 2 commits
-
-
Jacob Friedman authored
* Update init.mdx Updated operator init documentation to try to avoid steering customers towards running Auto Unseal seals with recovery-shares=1 and recovery-threshold=1. This is a bad security posture, as it can allow a single user with access to that recovery share to create root tokens and do other very sensitive tasks. Also rewrote parts of the HSM/KMS Options section to indicate that recovery-related options are not solely for HSM-mode Vault but are for ANY Auto Unseal seal. * Update website/content/docs/commands/operator/init.mdx Adding an appropriate number of recovery-pgp-keys Co-authored-by:
Yoko <yoko@hashicorp.com> Co-authored-by:
Yoko <yoko@hashicorp.com>
-
Angel Garbarino authored
-
- 03 Mar, 2021 5 commits
-
-
Brian Kassouf authored
-
Jim Kalafut authored
The existing code would retain the previous backoff value even after the system had recovered. This PR fixes that issue and improves the structure of the backoff code.
-
Theron Voran authored
Adds the option of a write-through cache, backed by boltdb Co-authored-by:
Theron Voran <tvoran@users.noreply.github.com> Co-authored-by:
Jason O'Donnell <2160810+jasonodonnell@users.noreply.github.com> Co-authored-by:
Calvin Leung Huang <cleung2010@gmail.com>
-
Vishal Nayak authored
-
Vishal Nayak authored
* k8s doc: update for 0.9.1 and 0.8.0 releases (#10825) * k8s doc: update for 0.9.1 and 0.8.0 releases * Update website/content/docs/platform/k8s/helm/configuration.mdx Co-authored-by:
Theron Voran <tvoran@users.noreply.github.com> Co-authored-by:
Theron Voran <tvoran@users.noreply.github.com> * Autopilot initial commit * Move autopilot related backend implementations to its own file * Abstract promoter creation * Add nil check for health * Add server state oss no-ops * Config ext stub for oss * Make way for non-voters * s/health/state * s/ReadReplica/NonVoter * Add synopsis and description * Remove struct tags from AutopilotConfig * Use var for config storage path * Handle nin-config when reading * Enable testing autopilot by using inmem cluster * First passing test * Only report the server as known if it is present in raft config * Autopilot defaults to on for all existing and new clusters * Add locking to some functions * Persist initial config * Clarify the command usage doc * Add health metric for each node * Fix audit logging issue * Don't set DisablePerformanceStandby to true in test * Use node id label for health metric * Log updates to autopilot config * Less aggressively consume config loading failures * Return a mutable config * Return early from known servers if raft config is unable to be pulled * Update metrics name * Reduce log level for potentially noisy log * Add knob to disable autopilot * Don't persist if default config is in use * Autopilot: Dead server cleanup (#10857) * Dead server cleanup * Initialize channel in any case * Fix a bunch of tests * Fix panic * Add follower locking in heartbeat tracker * Add LastContactFailureThreshold to config * Add log when marking node as dead * Update follower state locking in heartbeat tracker * Avoid follower states being nil * Pull test to its own file * Add execution status to state response * Optionally enable autopilot in some tests * Updates * Added API function to fetch autopilot configuration * Add test for default autopilot configuration * Configuration tests * Add State API test * Update test * Added TestClusterOptions.PhysicalFactoryConfig * Update locking * Adjust locking in heartbeat tracker * s/last_contact_failure_threshold/left_server_last_contact_threshold * Add disabling autopilot as a core config option * Disable autopilot in some tests * s/left_server_last_contact_threshold/dead_server_last_contact_threshold * Set the lastheartbeat of followers to now when setting up active node * Don't use config defaults from CLI command * Remove config file support * Remove HCL test as well * Persist only supplied config; merge supplied config with default to operate * Use pointer to structs for storing follower information * Test update * Retrieve non voter status from configbucket and set it up when a node comes up * Manage desired suffrage * Consider bucket being created already * Move desired suffrage to its own entry * s/DesiredSuffrageKey/LocalNodeConfigKey * s/witnessSuffrage/recordSuffrage * Fix test compilation * Handle local node config post a snapshot install * Commit to storage first; then record suffrage in fsm * No need of local node config being nili case, post snapshot restore * Reconcile autopilot config when a new leader takes over duty * Grab fsm lock when recording suffrage * s/Suffrage/DesiredSuffrage in FollowerState * Instantiate autopilot only in leader * Default to old ways in more scenarios * Make API gracefully handle 404 * Address some feedback * Make IsDead an atomic.Value * Simplify follower hearbeat tracking * Use uber.atomic * Don't have multiple causes for having autopilot disabled * Don't remove node from follower states if we fail to remove the dead server * Autopilot server removals map (#11019) * Don't remove node from follower states if we fail to remove the dead server * Use map to track dead server removals * Use lock and map * Use delegate lock * Adjust when to remove entry from map * Only hold the lock while accessing map * Fix race * Don't set default min_quorum * Fix test * Ensure follower states is not nil before starting autopilot * Fix race Co-authored-by:
Jason O'Donnell <2160810+jasonodonnell@users.noreply.github.com> Co-authored-by:
Theron Voran <tvoran@users.noreply.github.com>
-
- 02 Mar, 2021 2 commits
-
-
Michele Degges authored
-
Andrej van der Zee authored
-
- 01 Mar, 2021 8 commits
-
-
swayne275 authored
* sketch out partial month activity log client API * unit test partialMonthClientCount * cleanup api * add api doc, fix test, update api nomenclature to match existing * cleanup * add PR changelog file * integration test for API * report entities and tokens separately
-
Hridoy Roy authored
* minimal changes to solve most of the cves * cleanup * finished go mod vendor upgrades
-
Scott Miller authored
* Use the state lock, and don't bother a last minute check on seal * defer
-
-
Brian Kassouf authored
-
Chelsea Shaw authored
* Add test for db role setting form component * fix test, add changelog
-
Brian Kassouf authored
-
Scott Miller authored
* Documentation for barrier autorotation * changelog * 1.7 upgrade notes
-
- 27 Feb, 2021 1 commit
-
-
Brian Kassouf authored
* expiration: Add a few metrics to measure revoke queue lengths * Update the metric names * Add appropriate cluster labels * Add metrics to docs * Update jobmanager.go
-
- 26 Feb, 2021 10 commits
-
-
Michael Golowka authored
-
Meggie authored
-
Tom Proctor authored
-
Scott Miller authored
-
Angel Garbarino authored
* undo skip * add back settled
-
Jim Kalafut authored
* Replace deprecated terms in AWS Auth This PR is part of an effort to remove non-inclusive language throughout Vault. The AWS Auth backend uses the "whitelist" and "blacklist" term extensively, and these are the focus of the PR: * Add new API endpoints that use the preferred terminology, while deprecating the old endpoints. These endpoints offer identical functionality and are basically aliases. This is the only functional change in the PR except for terms in error messages. * Replace "whitelist" -> "access list", "blacklist" -> "deny list" in variable names, comments, etc. Note that storage locations were *not* changed at this time, as that is a more complex process involving versioning that we may tackle in a future revision. We have reduced the occurrences of non-inclusive language, however. Reviewers should be sure to "Ignore Whitespace" in diffs, especially for the tests, which were basically indented one level as part of l...
-
Chelsea Shaw authored
* Add tests for connection create and edit * Cleanup old tests, add role create form test * Fix linter/selector
-
Brian Kassouf authored
-
Brian Kassouf authored
-
Lauren Voswinkel authored
* Added support for iam_tags for AWS secret roles This change allows iam_users generated by the secrets engine to add custom tags in the form of key-value pairs to users that are created.
-
- 25 Feb, 2021 6 commits
-
-
Angel Garbarino authored
* fix KMIP test that was failing and clean modal on configuration page. * add changelog * remove uncessary unload * remove async
-
swayne275 authored
* stop fairsharing layer async * update function doc
-
Scott Miller authored
* Automatic barrier key rotation, OSS portion * Fix build issues * Vendored version * Add missing encs field, not sure where this got lost.
-
Michael Golowka authored
-
Michael Golowka authored
-
Meggie authored
1.6.3
-