Vault Export api changes to add first used timestamp column in query period docs change #697
Conversation
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
Vercel Previews Deployed
|
Broken Link Checker |
gsantos-hc
approved these changes
Aug 6, 2025
content/vault/v1.21.x (rc)/content/api-docs/system/internal-counters.mdx
Outdated
Show resolved
Hide resolved
content/vault/v1.21.x (rc)/content/api-docs/system/internal-counters.mdx
Outdated
Show resolved
Hide resolved
|
It looks like token creation time is the creation time of the token that was used to perform the request for the client and this necessarily need not be the first ever token created for the client. I modified the description as part of commit 704966f |
schavis
requested changes
Aug 7, 2025
content/vault/v1.21.x (rc)/content/api-docs/system/internal-counters.mdx
Outdated
Show resolved
Hide resolved
content/vault/v1.21.x (rc)/content/api-docs/system/internal-counters.mdx
Outdated
Show resolved
Hide resolved
|
|
||
| - `client_first_usage_time` in the response is a timestamp that represents the earliest usage of the client during the queried time period. | ||
|
|
||
| - **`sudo` required** – This endpoint requires `sudo` capability in addition to |
There was a problem hiding this comment.
Suggest deleting the sudo line in favor of using the restricted endpoint partial directly below the "Activity export" heading
There was a problem hiding this comment.
I think this is more of a policy capability rather than a root-restricted endpoint
content/vault/v1.21.x (rc)/content/api-docs/system/internal-counters.mdx
Show resolved
Hide resolved
…unters.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
…unters.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
schavis
approved these changes
Aug 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Jira: https://hashicorp.atlassian.net/browse/VAULT-37796
Adds client_first_usage_time to export api
Looks like token_creation_time ce changes are not present in this repo. Added those changes too https://github.com/hashicorp/vault/pull/31149/files