Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of Update vault-plugin-secrets-azure to v0.21.1 into release/1.19.x #29732

Conversation

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

Backport

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

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


This PR was generated by a GitHub Action. Full log: https://github.com/hashicorp/vault/actions/runs/13554596945


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/VAULT-34110/update/vault-plugin-secrets-azure/v0.21.1/wrongly-famous-troll branch from d6255a0 to 2f16560 Compare February 26, 2025 22:50
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Feb 26, 2025
Copy link

github-actions bot commented Feb 26, 2025

Build Results:
All builds succeeded! ✅

Copy link

github-actions bot commented Feb 26, 2025

CI Results:
All Go tests succeeded! ✅

@kpcraig kpcraig added this to the 1.19.0 milestone Feb 27, 2025
…plugin-secrets-azure/v0.21.1/wrongly-famous-troll
@kpcraig kpcraig enabled auto-merge (squash) February 27, 2025 00:37
@kpcraig kpcraig merged commit 1561a1b into release/1.19.x Feb 27, 2025
85 checks passed
@kpcraig kpcraig deleted the backport/VAULT-34110/update/vault-plugin-secrets-azure/v0.21.1/wrongly-famous-troll branch February 27, 2025 00:49
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants