Skip to content

Update clientcountutil to accommodate entity record usage time changes CE changes#31301

Merged
akshya96 merged 7 commits into
mainfrom
vault-37795-ce
Jul 22, 2025
Merged

Update clientcountutil to accommodate entity record usage time changes CE changes#31301
akshya96 merged 7 commits into
mainfrom
vault-37795-ce

Conversation

@akshya96
Copy link
Copy Markdown
Contributor

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 Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.
    • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
  • ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
    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.
  • Jira: If this change has an associated Jira, it's referenced either
    in the PR description, commit message, or branch name.
  • RFC: If this change has an associated RFC, please link it in the description.
  • ENT PR: If this change has an associated ENT PR, please link it in the
    description. Also, make sure the changelog is in this PR, not in your ENT PR.

PCI review checklist

  • I have documented a clear reason for, and description of, the change I am making.
  • If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
  • If applicable, I've documented the impact of any changes to security controls.

Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

@akshya96 akshya96 requested a review from a team as a code owner July 16, 2025 22:26
@github-actions github-actions Bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Jul 16, 2025
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jul 16, 2025

CI Results:
All Go tests succeeded! ✅

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jul 16, 2025

Build Results:
All builds succeeded! ✅

aslamovamir
aslamovamir previously approved these changes Jul 17, 2025
Comment thread vault/logical_system_activity_write_testonly.go
Comment thread helper/timeutil/timeutil.go Fixed
@akshya96 akshya96 requested review from aslamovamir and divyaac July 21, 2025 22:42
@akshya96 akshya96 enabled auto-merge (squash) July 22, 2025 16:59
@akshya96 akshya96 merged commit 1fb0066 into main Jul 22, 2025
85 of 86 checks passed
@akshya96 akshya96 deleted the vault-37795-ce branch July 22, 2025 17:20
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed pr/no-changelog pr/no-milestone

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants