Skip to content

Backport of VAULT-35602: Adding Enos OpenLDAP test into release/1.20.x#31362

Merged
tvo0813 merged 1 commit into
release/1.20.xfrom
backport/enos/VAULT-35602/globally-ultimate-mustang
Jul 28, 2025
Merged

Backport of VAULT-35602: Adding Enos OpenLDAP test into release/1.20.x#31362
tvo0813 merged 1 commit into
release/1.20.xfrom
backport/enos/VAULT-35602/globally-ultimate-mustang

Conversation

@hc-github-team-secure-vault-core
Copy link
Copy Markdown
Collaborator

Backport

This PR is auto-generated from #30801 to be assessed for backporting due to the inclusion of the label backport/1.20.x.

The below text is copied from the body of the original PR.


Description

VAULT-35602: Adding Enos OpenLDAP test

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.

Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/enos/VAULT-35602/globally-ultimate-mustang branch from 1f65b9b to a896051 Compare July 23, 2025 20:11
@github-actions github-actions Bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Jul 23, 2025
@github-actions
Copy link
Copy Markdown

CI Results:
All Go tests succeeded! ✅

@tvo0813 tvo0813 force-pushed the backport/enos/VAULT-35602/globally-ultimate-mustang branch from a896051 to 6e1bc8f Compare July 23, 2025 20:18
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jul 23, 2025

Build Results:
All builds succeeded! ✅

@tvo0813 tvo0813 force-pushed the backport/enos/VAULT-35602/globally-ultimate-mustang branch from 6e1bc8f to 8dcbd50 Compare July 23, 2025 20:48
@tvo0813 tvo0813 force-pushed the backport/enos/VAULT-35602/globally-ultimate-mustang branch from 8dcbd50 to 3a0a4ed Compare July 24, 2025 18:20
@vercel
Copy link
Copy Markdown

vercel Bot commented Jul 24, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
vault-ui ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 28, 2025 7:00pm

@tvo0813 tvo0813 force-pushed the backport/enos/VAULT-35602/globally-ultimate-mustang branch from 0efa446 to c12a2c0 Compare July 28, 2025 19:00
@tvo0813 tvo0813 merged commit 6d284fb into release/1.20.x Jul 28, 2025
51 checks passed
@tvo0813 tvo0813 deleted the backport/enos/VAULT-35602/globally-ultimate-mustang branch July 28, 2025 20:07
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.

3 participants