Closed maxlaverse closed 1 year ago
I realized this error is not supposed to happen, as we translate this specific Not found.
output into an object not found
error: https://github.com/maxlaverse/terraform-provider-bitwarden/blob/6ce0c3f9f83faf9357acc4e3860d01f5f3bf0ec0/internal/bitwarden/bw/client.go#L153-L155
I'm thinking this could be the non-thread safe bytes.Buffer messing up with the output, which would eventually not match what we're looking for: https://github.com/maxlaverse/terraform-provider-bitwarden/blob/6ce0c3f9f83faf9357acc4e3860d01f5f3bf0ec0/internal/command/cmd.go#L61-L73
I'll try to simplify this method and see if the problem occurs again
Couldn't reproduce. I'll assume it fix but we can re-open it if necessary
Issue created out of https://github.com/maxlaverse/terraform-provider-bitwarden/issues/61, reported by @leynebe
Terraform Version
Affected Resource(s)
bitwarden_item_login
Terraform Configuration Files
Debug Output
No debug output yet
Panic Output
No panic output
Expected Behavior
Items should have been refreshed during planning
Actual Behavior
Errors with 404s not found
Steps to Reproduce
Issue happen to @leynebe
It happened to me as well after removing the local Vault
Important Factoids
Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?
References
Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example: