Ui/upgrade date fns#9523
Closed
andaley wants to merge 231 commits into
Closed
Conversation
For situations where you want the Vault agent to handle one or more templates but do not require the acquired credentials elsewhere. Modify the logic in SyncServer so that if there are no sinks, ignore any new credentials. Since SyncServer is responsible for shutting down the agent, make sure it still properly shuts down in this new situation. Solves #7988
…8637) * Add random string generator with rules engine This adds a random string generation library that validates random strings against a set of rules. The library is designed for use as generating passwords, but can be used to generate any random strings.
Fixing a version typo in 1.3.6 notes.
* Populate a token_ttl and token_issue_time field on the Auth struct of audit log entries, and in the Auth portion of a response for login methods * Revert go fmt, better zero checking * Update unit tests * changelog++
…et re-rendered. (#9097)
Syntax for sockaddr.is_contained should be outer, inner - i.e. range, IP. See https://docs.hashicorp.com/sentinel/imports/sockaddr/ for reference.
* Refactor PG container creation. * Rework rotation tests to use shorter sleeps. * Refactor rotation tests. * Add a static role rotation test for MongoDB Atlas.
* Add docs for password policies
* Update OpenLDAP docs to use password policies
* Add token creation counters. * Created a utility to change TTL to bucket name. * Add counter covering token creation for response wrapping. * Fix namespace label, with a new utility function.
* Adding changes for vault-k8s 0.4.0 * add note about run-as-same-user rejecting root
* Docs updates for vault-helm 0.6.0 release * added openshift and postStart values * noting that openshift support is a beta feature
* Adds ability to use password policies Operations: Updated go.mod for OpenLDAP to v0.1.3 Ran `go mod tidy` Ran `go mod vendor`
* Fix issue migrating from Auto->Shamir and improve tests * Undo newline * fix panic in test * Fix test panic
* physical/gcs: use separate client for updating locks * Address review comments Co-authored-by: Calvin Leung Huang <cleung2010@gmail.com>
* physical/spanner: use separate client for updating locks We believe this mitigates an issue where a large influx of requests cause the leader to be unable to update the lock table (since it cannot grab a client from the pool or the client has no more open connections), which causes cascading failure.
* fix linting errors * don't show primary url if we don't have any primaries * Revert "fix linting errors" This reverts commit a56d371. * run all component tests always
…to NewTestCluster. (#9451)
* Adding notes about ingress and route requirements Specifically that they require vault 1.4 with service_registration enabled. Also removed a stray block about extraVolumes.
…dling of non-ISO date strings
andaley
force-pushed
the
ui/upgrade-date-fns
branch
from
0885b4b to
ffcd078
Compare
pull Bot
pushed a commit
to Reality2byte/vault
that referenced
this pull request
Sep 23, 2025
* updating go-discover * adding changelog * adjusting changelog --------- Co-authored-by: JMGoldsmith <spartanaudio@gmail.com> Co-authored-by: Tony Wittinger <anwittin@users.noreply.github.com>
tsaarni
pushed a commit
to Nordix/vault
that referenced
this pull request
Sep 25, 2025
…ashicorp#9574) * updating go-discover * adding changelog * adjusting changelog --------- Co-authored-by: JMGoldsmith <spartanaudio@gmail.com> Co-authored-by: Tony Wittinger <anwittin@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update date-fns
Update date-fns to 2.0.0 which requires us update all of our date-related helpers. The most notable change we had to account for is that all of the date-fns functions no longer accept strings as arguments. You'll notice we also had to switch some of the formatting arguments from
YYYYtoyyyyas a result. See the full list of breaking changes when upgrading to date-fns 2.0.0 here.Testing
This PR requires a considerable QA as it changes the behavior of our
date-from-nowanddate-formathelpers. We now return an empty string and console log an error if the formatting doesn't work, so there's a chance some dates may be missing in the UI.Navigate to the various pages of the UI where
date-formatordate-from-nowis used, such as the replication secondaries add modal which displays the expiration date. These pages should still display the date as expected.Here's an example of the replication secondaries add modal:
