maxexcloo
commented
4 months ago Seems to be an issue since version 2.0.0 which was released just a few hours ago...
Open maxexcloo opened 4 months ago
maxexcloo
commented
4 months ago Seems to be an issue since version 2.0.0 which was released just a few hours ago...
maxexcloo
commented
4 months ago This seems to be because my label for the section was empty, worked before and would like to keep using this behavior.
section {
label = ""
...
}
pro4tlzz
commented
4 months ago This seems to be because my label for the section was empty, worked before and would like to keep using this behavior.
section { label = "" ... }
I'm setting a value both for the label within the section and the field but also experiencing an error.
│ Error: Provider produced inconsistent result after apply
--
| │
| │ When applying changes to onepassword_item.super_secret_credential, provider "provider[\"registry.terraform.io/1password/onepassword\"]" produced an unexpected new value: .note_value: inconsistent values for sensitive attribute.
| │
| │ This is a bug in the provider, which should be reported in the provider's own issue tracker.
Terraform v1.7.5 provider registry.terraform.io/1password/onepassword 2.0.0 OS: Linux
Edit: ignore that actually, we were using the resource section incorrectly
DavidS-ovm
commented
3 months ago @pro4tlzz can you share a hint how you were using sections incorrectly? I'm also running into this issue, the item gets created just fine with all sections labeled, and I still get the "inconsistent values for sensitive attribute" errors...
DavidS-ovm
commented
3 months ago Further experimentation surfaced that the provider is not able to deal with empty values. I'll create a separate ticket for that. [edit: #185]
pro4tlzz
commented
3 months ago @pro4tlzz can you share a hint how you were using sections incorrectly? I'm also running into this issue, the item gets created just fine with all sections labeled, and I still get the "inconsistent values for sensitive attribute" errors...
Changed from something like
section {
label = "REDACTED"
field {
label = "Instructions"
purpose = "NOTES"
type = "STRING"
value = <<EOT
REDACTED
EOT
}
}
}to
title = "REDACTED"
category = "login"
url = "REDACTED"
username = "REDACTED"
password = "REDACTED"
note_value = <<EOT
REDACTED
EOTBasically don't use section or field as objects, just set all these properties in the root context of the resource
JBG-brad
commented
2 months ago Just chiming in here that I had this same problem.
Since the types of documents that can be created are so limited, I use "login" and create sections. To avoid confusion, I used to est the username to "".
Setting the username to something aside from an empty string fixed the issue.
username = "none"```
Your environment
Terraform Provider Version: 2.0.0 CLI Version: 2.28.0 OS: macOS 14.5 Terraform Version: OpenTofu v1.7.1
What happened?
Was working fine, suddenly getting errors on apply today (even though resources haven't changed). Deleted resources in state and in the vault and attempted to recreate.
What did you expect to happen?
Update went as planned.
Notes & Logs