Update clientcountutil to accommodate entity record usage time changes CE changes#31301
Merged
Conversation
|
CI Results: |
|
Build Results: |
aslamovamir
previously approved these changes
Jul 17, 2025
divyaac
approved these changes
Jul 21, 2025
divyaac
requested changes
Jul 21, 2025
divyaac
approved these changes
Jul 22, 2025
Erfankam
pushed a commit
to Erfankam/vault
that referenced
this pull request
Sep 1, 2025
…s CE changes (hashicorp#31301) * moving clientcountutil changes from ent * adding random usage time for repeated clients * replace math.rand with crypto.rand
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
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.
Description
What does this PR do?
Jira: https://hashicorp.atlassian.net/browse/VAULT-37795
Update usage time to entity record in clientcountutil.
ENT changes: https://github.com/hashicorp/vault-enterprise/pull/8471 to verify if tests pass on ENT.
These changes will be used when we add export api changes to show first used time in billing period
Will add changelog to export api changes PR
TODO only if you're a HashiCorp employee
backport/label that matches the desired release branch. Note that in the CE repo, the latest release branch will look likebackport/x.x.x, but older release branches will bebackport/ent/x.x.x+ent.of a public function, even if that change is in a CE file, double check that
applying the patch for this PR to the ENT repo and running tests doesn't
break any tests. Sometimes ENT only tests rely on public functions in CE
files.
in the PR description, commit message, or branch name.
description. Also, make sure the changelog is in this PR, not in your ENT PR.
PCI review checklist
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.