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

Terraform shouldn't error when we cannot find a secret by ID, as we may need to recreate a manually deleted secret #191

Open
josh-thisisbud opened this issue Aug 6, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@josh-thisisbud
Copy link

resp.Diagnostics.AddError("1Password Item read error", fmt.Sprintf("Could not get item '%s' from vault '%s', got error: %s", itemUUID, vaultUUID, err))

This line here shouldn't be bombing out during a terraform run, as it's entirely valid that the secret may have been deleted and we need to recreate it. I'd suggest turning this into a warning at most, so that people can learn that it happened from logging?

@garbelini
Copy link

Agreed. Providers should not error on 404s.

Seems like the code delegates the call to the cli that fails when an item is not found. That's appropriate for a cli but not for a terraform provider.

@SimonBarendse SimonBarendse added the bug Something isn't working label Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants