When starting a vault dev server the token helper is invoked to store
the dev root token.
This option gives the user the ability to not store the token.
Storing the token can be undesirable in certain circumstances
(e.g. running local tests) as the user's existing vault token is
clobbered without warning.
Fixes#1861
We're waiting to see standbys receive wals but aren't generating traffic, so the condition is never satisfied. Fixed by continuously updating a KV value. It's a little weird to do so in each of the
goroutines, but there's no harm and it's simplest.
* ci: re-enable browserstack tests ...
- Also sets "strict mode" bash with -euo pipefail at executor level.
* ci: Makefile: more compatible SHELL var
* ci: remove some trailing whitespace
* ci: remove redundant set -eux -o pipefail
- In some cases, just replace with -x where debug output might be useful.
- In most cases, don't bother with -x, it is a secret leak risk, and
circleci prints the command body before executing it anyway.
* try specifying yarn version
* set yarn version
* Revert "try specifying yarn version"
This reverts commit 6b4e57a304d999d72d4b07468a6b4a30880f1f4c.
* always use ?force for kmip scope delete
* update the delete message when deleting a scope
* support disabling and not showing help text for checkboxes
* group TLS fields and render new allowed operations widget
* add operation-field-display component for kmip roles
* use operation-field-display component
* switch glyph for false value in info-table-row
* divvy up roles and tls
* fix JSDoc - showHelpText defaults to true
* fix tests and linting
* rename vars in operation-field-display component
* make the action name clearer re: what it's actually doing
* align the allowed-ops header
* show all operations as checked if you check to allow all
This eliminates a bunch of noise at the end of a test's logs, making it
easier to diagnose test failures.
Add TestCluster.Logger. This is intendend to be used when test helpers
want to log something. If TestClusterOptions.Logger is non-nil, it will
be used as the cluster logger, otherwise we create one based on test
name. In the absence of CoreConfig.Logger, this logger is also used as
the parent of each core's log. This makes it easy when running parallel
tests to identify which log message came from which test.
Various improvements to testhelpers.
* WaitForActiveNodeAndPerfStandbys is used to make sure a cluster is fully ready, i.e. both its active node and perf standbys are in a good state.
* WaitForReplicationStatus is like WaitForReplicationState but uses the API, part of a general
effort to move us away from interacting with Core directly in these tests.
* WaitForPerfReplicationWorking is similar to some code that exists in ent already: it writes to the primary and waits to see that appear on the secondary.
its timeout from 5s to 15s in the hopes that helps. The theory is that
since I haven't seen this on the OSS side, it's failing because the ent
side is heavier in terms of test load and thus the tests face more
resource contention.
* flush identity/oidc cache by namespace
* separates and unit tests the logic that looks for a namespace id within a namespace key
* applies pr feedback
* renames nskeyContainsID to isNamespacedKey
We already have a separate log line if rollback fails. It really fills
up logs to always note when rollback is occurring and it usually isn't
useful for incidents.
* Read config before creating logger when booting vault server
* Allow for specifying log output in JSON format in a config file, via a 'log_level' flag
* Create parser for log format flag
* Allow for specifying log format in a config file, via a 'log_format' flag. Also, get rid of 'log_json' flag.
* Add 'log-format' command line flag
* Update documentation to include description of log_format setting
* Tweak comment for VAULT_LOG_FORMAT environment variable
* add test for ParseEnvLogFormat()
* clarify how log format is set
* fix typos in documentation
