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

chore(deps): update hashicorp/vault-action action to v2.7.4 #129

Merged
merged 1 commit into from
Dec 4, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 26, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change
hashicorp/vault-action action minor v2.5.0 -> v2.7.4
hashicorp/vault-action action patch v2.7.3 -> v2.7.4

Release Notes

hashicorp/vault-action (hashicorp/vault-action)

v2.7.4

Compare Source

2.7.4 (October 26, 2023)

Features:

  • Add ability to specify a wildcard for the key name to get all keys in the path GH-488

v2.7.3

Compare Source

2.7.3 (July 13, 2023)

Bugs:

  • Revert to the handling of secrets in JSON format since v2.1.2 GH-478

v2.7.2

Compare Source

2.7.2 (July 6, 2023)

Bugs:

  • Fix a regression that broke support for secrets in JSON format GH-473

v2.7.1

Compare Source

2.7.1 (July 3, 2023)

Bugs:

  • Revert GH-466 which caused a regression in secrets stored as JSON strings GH-471

v2.7.0

Compare Source

Bugs:

  • Fix a regression that broke support for secrets in JSON format GH-466

Improvements:

  • Fix a warning about outputToken being an unexpected input GH-461

v2.6.0

Compare Source

2.6.0 (June 7, 2023)

Features:

  • Add ability to set the vault_token output to contain the Vault token after authentication GH-441
  • Add support for userpass and ldap authentication methods GH-440
  • Define an output, errorMessage, for vault-action's error messages so subsequent steps can read the errors GH-446

Bugs:

  • Handle undefined response in getSecrets error handler GH-431

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/hashicorp-vault-action-2.x branch from 6b494ad to c9382a9 Compare November 1, 2023 16:34
@renovate renovate bot force-pushed the renovate/hashicorp-vault-action-2.x branch from c9382a9 to b796416 Compare December 4, 2023 19:07
@InversionSpaces InversionSpaces requested a review from nahsi December 4, 2023 19:07
@renovate renovate bot force-pushed the renovate/hashicorp-vault-action-2.x branch from b796416 to 2948f99 Compare December 4, 2023 19:11
@renovate renovate bot force-pushed the renovate/hashicorp-vault-action-2.x branch from 2948f99 to 253e10d Compare December 4, 2023 19:17
@nahsi nahsi merged commit 1e10df9 into main Dec 4, 2023
5 of 6 checks passed
@nahsi nahsi deleted the renovate/hashicorp-vault-action-2.x branch December 4, 2023 19:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant