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

Upgrade terraform-provider-vault to v3.18.0 #272

Closed
pulumi-bot opened this issue Jul 12, 2023 · 5 comments · Fixed by #296
Closed

Upgrade terraform-provider-vault to v3.18.0 #272

pulumi-bot opened this issue Jul 12, 2023 · 5 comments · Fixed by #296
Assignees
Labels
kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Milestone

Comments

@pulumi-bot
Copy link
Contributor

Release details: https://github.com/hashicorp/terraform-provider-vault/releases/tag/v3.18.0

@pulumi-bot pulumi-bot added the kind/enhancement Improvements or new features label Jul 12, 2023
@kwohlfahrt
Copy link

kwohlfahrt commented Jul 24, 2023

I'm interested in this bump, as it fixes this issue: hashicorp/terraform-provider-vault#1932

Edit: Actually, nevermind. client_flag is still broken in that release, I've opened hashicorp/terraform-provider-vault#1952

@mikhailshilkov mikhailshilkov added the blocked The issue cannot be resolved without 3rd party action. label Jul 26, 2023
@iwahbe
Copy link
Member

iwahbe commented Aug 2, 2023

@mikhailshilkov why is this blocked?

@aureq
Copy link
Member

aureq commented Aug 23, 2023

@iwahbe maybe because hashicorp/terraform-provider-vault#1952 wasn't closed at the time. I just checked and it seems to be fixed.

@mikhailshilkov any chance we could get this unblocked as we have a customer looking at v3.19.0 already due to another blocking issue for them.

@iwahbe
Copy link
Member

iwahbe commented Aug 24, 2023

@lukehoban is this good to upgrade? We will be targeting #289.

@lukehoban lukehoban removed the blocked The issue cannot be resolved without 3rd party action. label Aug 24, 2023
@lukehoban
Copy link

@lukehoban is this good to upgrade? We will be targeting #289.

Yes - good to update to 3.19.0.

@iwahbe iwahbe self-assigned this Aug 24, 2023
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label Aug 24, 2023
@mikhailshilkov mikhailshilkov added this to the 0.93 milestone Aug 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants