From cb32091872239337f38bfbf272567437c777523b Mon Sep 17 00:00:00 2001 From: Ansgar Mertens Date: Mon, 18 Mar 2024 09:40:37 +0100 Subject: [PATCH] chore: upgrade vault provider version to 4.0 (#281) ### Related issue Fixes # ### Description In plain English, describe your approach to addressing the issue linked above. For example, if you made a particular design decision, let us know why you chose this path instead of another solution. ### Checklist - [ ] I have updated the PR title to match [CDKTF's style guide](https://github.com/cdktf/.github/blob/main/CONTRIBUTING.md#pull-requests-1) - [ ] I have run the linter on my code locally - [ ] I have performed a self-review of my code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation if applicable - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works if applicable - [ ] New and existing unit tests pass locally with my changes --- provider.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/provider.json b/provider.json index cbded86..377aceb 100644 --- a/provider.json +++ b/provider.json @@ -42,6 +42,6 @@ "time": "hashicorp/time@~> 0.7", "tls": "hashicorp/tls@~> 4.0", "upcloud": "UpCloudLtd/upcloud@~> 5.0", - "vault": "hashicorp/vault@~> 3.7", + "vault": "hashicorp/vault@~> 4.0", "vsphere": "vsphere@~> 2.2" }