Closed Sayrus closed 2 weeks ago
Came here after issues search for the same thing. Would be very nice to have in the next release.
Hi @fairclothjm, I was wondering when the new version of the provider will be available please? I've noticed the allow_empty_principals
field is not yet available and unfortunately, this has been causing us issues. Also, is there any workaround that we can put in place at all until the flag is released?
Many thanks! :)
Hi @lauracraciun90 ! I am sorry you are having issues. We try to do a release in the middle of each month. We are planning to do one within the week.
Unfortunately, I don't have any workarounds at this time.
Hi @fairclothjm, thanks very much indeed for your reply :) That's good to know - will wait for the new release to become available in the next few days. That's ok, no problem at all. May thanks for your help!
@lauracraciun90 https://github.com/hashicorp/terraform-provider-vault/releases/tag/v4.5.0 😄
Hi @fairclothjm thanks very much for the update! :)
I've upgraded the vault provider to version 4.50 and tried to incorporate the flag in our setup, however, it still doesn't fix the problem for us.
Should the field be used within the vault_ssh_secret_backend_role
resource? If so, it looks like the argument is not supported by terraform and I'm getting an "unsupported argument" error.
I've also tried to add the flag to the API call to Vault, however, this doesn't work either, and I'm still getting the empty service principals error.
Please could you give me some more info on this if possible? Many thanks!
Description
https://github.com/hashicorp/vault/pull/28466 introduces a breaking change (Vault 1.18, backported to 1.17) for SSH Backend by disallowing empty roles by default. Unfortunately, it is currently not possible to set
allow_empty_principals
from Terraform.Sign done without principals return:
Affected Resource(s) and/or Data Source(s)
Potential Terraform Configuration
References
https://github.com/hashicorp/vault/pull/28466
Would you like to implement a fix?
None