Open ivankatliarchuk opened 7 months ago
Looks like I may be hitting this as well. Using the example code https://registry.terraform.io/providers/hashicorp/vault/latest/docs/resources/generic_endpoint#example-usage "u1_entity" I'm also getting the Code 405 error.
I noticed that the error shows URL: GET https://vault.local:8200/v1/identity/lookup/entity however when I successfully run this command via CLI it's uses PUT via vault write command instead.
I suspect that this resource is not sending the correct command and ignoring the configuration of disable_read
terraform v1.6.4 vault provider v3.23.0
Update: I revisited this config with fresh eyes. it appears that because I used vault_generic_endpoint without disable_read = true once it was preventing any further plan from succeeding. Once I did a terraform state rm to that resource and applied again with disable_read = true it worked as expected. So watch out for that trap with vault_generic_endpoint.
I'll re-test. I think I did cover this case too and the behavior was the same.
Happening to me as well. Hit this issue after being redirect from https://github.com/hashicorp/terraform-provider-vault/issues/1715.
Hit this as well, does anyone have a workaround? Thanks in advance
Changes published here are causing that: https://registry.terraform.io/providers/hashicorp/vault/latest/docs/guides/version_4_upgrade
Terraform Core Version
1.5.5
Terraform Vault Provider Version
3.23.0
Vault Server Version
1.15.1
Affected Resource(s)
Expected Behavior
The resource will get deleted from state file
Actual Behavior
Why using
vault_generic_endpoint
fordisalbe_upsert
. https://github.com/hashicorp/terraform-provider-vault/issues/2091Relevant Error/Panic Output Snippet
On apply
Steps to Reproduce
Minimal reproduction snippet
Note: default value is
false
, so in reality nothing is change step 1. plan and apply step 2. comment out resourcevault_generic_endpoint
step 3. plan and apply result: errorDebug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None