Closed krarey closed 1 year ago
Hi @krarey, you are correct that this is currently an issue. This is due to the Terraform SDK that we are using and I'm working on a new version of the provider that should fix this issue and other similar that are currently present in the provider.
Terraform Version
Terraform v1.3.1 on linux_amd64
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
The Consul Connect certificate authority should be correctly configured with the associated Vault auth method details, in place of requiring a hardcoded token. See the Consul documentation for details on the
auth_method
schema.Actual Behavior
Terraform fails to plan, citing type mismatch (expected
string
, receivedmap
). Attempting to work around by using jsonencode() or otherwise converting to a string fails, as the Consul API rejects the configuration.