You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 8, 2022. It is now read-only.
auth0_connection.user-pass-auth: Creating...
Error: 400 Bad Request: Payload validation error: 'Expected type boolean but found type null' on property options.password_no_personal_info.enable.
on auth0.tf line 99, in resource "auth0_connection" "user-pass-auth":
99: resource "auth0_connection" "user-pass-auth" {
Expected Behavior
Provider/API should accept boolean values.
Actual Behavior
Terraform throws the error above for boolean values in the options block. The message 'Expected type boolean but found type null' sounds like Terraform doesn't get the value correctly. A null is read instead of a false.
Steps to Reproduce
Use the HCL code above and insert valid values for client_id and audience. For scope only a empty list.
This issue is stale because it has been open 30 days with no activity.
Stale issues will be closed after 5 days if no action is taken. If you
think this issue should not be closed, remove the stale label.
Community Note
Terraform Version
Terraform v0.12.19,
terraform-provider-auth0 v0.4.3
Affected Resource(s)
Terraform Configuration Files
Debug Output
Not that long, therefore no gist. :)
Expected Behavior
Provider/API should accept boolean values.
Actual Behavior
Terraform throws the error above for boolean values in the options block. The message
'Expected type boolean but found type null'
sounds like Terraform doesn't get the value correctly. A null is read instead of a false.Steps to Reproduce
terraform apply
Important Factoids
None
References
Seems to be related to Issue 159
The text was updated successfully, but these errors were encountered: