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
│ Error: Plugin did not respond
│
│ with elasticsearch_role.test,
│ on main.tf line 56, in resource "elasticsearch_role" "test":
│ 56: resource elasticsearch_role "test" {
│
│ The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ApplyResourceChange call. The plugin logs may
│ contain more details.
╵
Stack trace from the terraform-provider-elasticsearch_v7.0.4.exe plugin:
panic: interface conversion: interface {} is nil, not *elasticsearch.Client
Error: The terraform-provider-elasticsearch_v7.0.4.exe plugin crashed!
This is always indicative of a bug within the plugin. It would be immenselyhelpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.
The text was updated successfully, but these errors were encountered:
│ Error: Plugin did not respond
│
│ with elasticsearch_role.test,
│ on main.tf line 56, in resource "elasticsearch_role" "test":
│ 56: resource elasticsearch_role "test" {
│
│ The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ApplyResourceChange call. The plugin logs may
│ contain more details.
╵
Stack trace from the terraform-provider-elasticsearch_v7.0.4.exe plugin:
panic: interface conversion: interface {} is nil, not *elasticsearch.Client
goroutine 117 [running]:
github.com/disaster37/terraform-provider-elasticsearch/v7/es.createRole(0xc000421420, 0x0, 0x0, 0x0, 0x0)
github.com/disaster37/terraform-provider-elasticsearch/v7/es/resource_elasticsearch_security_role.go:306 +0xb75
github.com/disaster37/terraform-provider-elasticsearch/v7/es.resourceElasticsearchSecurityRoleCreate(0xc000421420, 0x0, 0x0, 0x2, 0x207ce80)
google.golang.org/[email protected]/server.go:708 +0xa8
Error: The terraform-provider-elasticsearch_v7.0.4.exe plugin crashed!
This is always indicative of a bug within the plugin. It would be immenselyhelpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.
The text was updated successfully, but these errors were encountered: