Closed irons closed 7 months ago
When I passed in an invalid date format, I noticed the Terraform provider hinted about the format.
Since so many applications use RFC3339 to exchange dates I made a feature request #135 to support it.
Currently, the valid format is YYYY-MM-DD
. It will print more user-friendly error in this PR #150
See the documentation for the details
Your environment
Terraform Provider Version: 1.0.2
Connect Server Version: 1.2.0
OS: macOS 11.6.1
Terraform Version: 1.0.6
What happened?
I've been unable to find acceptable Terraform syntax for creating a date-typed 1Password field. Attempts so far have all resulted in "400 Bad Request" results back from
terraform apply
. Here are five potential formats that I've tried, along with one string-typed field to show that the date formatting succeeds.What did you expect to happen?
I expected at least one of those five value-setting lines to set a value without an error. I arrived at the 1635800957 epoch date by looking at how the JSON data came back from the op CLI after setting a date field interactively, but setting it also failed.
Ideally, I'd like to find a date format acceptable to 1Password Connect's Terraform provider that can be emitted by Terraform's formatdate function (epoch date is not on that list).
Steps to reproduce
Notes & Logs