terraform-provider-mongodbatlas_v1.6.0 plugin crashed

[ppiankov]

Terraform CLI and Terraform MongoDB Atlas Provider Version

❯ terraform version
Terraform v1.3.5
on darwin_amd64
+ provider registry.terraform.io/hashicorp/aws v4.40.0
+ provider registry.terraform.io/hashicorp/kubernetes v2.16.0
+ provider registry.terraform.io/mongodb/mongodbatlas v1.6.0

same was with
Terraform v1.3.3

Terraform Configuration File

terraform {
  required_providers {
    mongodbatlas = {
      source = "mongodb/mongodbatlas"
      version = "1.6.0"
    }
  }
}

resource "mongodbatlas_search_index" "textSearch" {
  name = "textSearch"
  project_id = local.mdb_project_id
  cluster_name = local.mdb_cluster_main

  analyzer = "lucene.standard"
  collection_name = "offers"
  database = "offers-test"
  mappings_dynamic = false
  mappings_fields = <<-EOF
{
  "brand": {
    "fields": {
      "name": {
        "analyzer": "lucene.standard",
        "searchAnalyzer": "lucene.standard",
        "type": "string",
        "norms": "omit",
      }
    },
    "type": "document"
  },
  "settings": {
    "fields": {
      "description": {
        "analyzer": "lucene.standard",
        "searchAnalyzer": "lucene.standard",
        "type": "string",
        "norms": "omit"
      },
      "title": {
        "analyzer": "lucene.standard",
        "searchAnalyzer": "lucene.standard",
        "type": "string",
        "norms": "omit"
      }
    },
    "type": "document"
  }
}
EOF

  search_analyzer = "lucene.standard"
}

Steps to Reproduce

1. terraform init
2. terraform apply

Expected Behavior

the existing index should get updated

Actual Behavior

crash dump

Crash Output

https://gist.github.com/ppiankov/2ed7249c41f942bdf9f179fd2e8bc3fa

[evertsd]

@ppiankov Based on this, it looks like an issue with the provider not being able to handle going from a non-nil value of search_analyzer to value nil.

A potential workaround may be adding search_analyzer = "" to your mongodbatlas_search_index.textSearch resource

[ppiankov]

thanks search_analyzer = "" helped.

[ppiankov]

but after this fix the index is not working at all

[evertsd]

Did you still need the following?

search_analyzer = "lucene.standard"

Or does including the above cause the crash output in the gist?

[ppiankov]

yes if we include

search_analyzer = "lucene.standard"

it will crash.

and this is how a healthy working index created manually looks like

{
  "analyzer": "lucene.standard",
  "mappings": {
    "dynamic": false,
    "fields": {
      "brand": {
        "fields": {
          "name": {
            "analyzer": "lucene.standard",
            "norms": "omit",
            "searchAnalyzer": "lucene.standard",
            "type": "string"
          }
        },
        "type": "document"
      },
      "settings": {
        "fields": {
          "description": {
            "analyzer": "lucene.standard",
            "norms": "omit",
            "searchAnalyzer": "lucene.standard",
            "type": "string"
          },
          "title": {
            "analyzer": "lucene.standard",
            "norms": "omit",
            "searchAnalyzer": "lucene.standard",
            "type": "string"
          }
        },
        "type": "document"
      }
    }

[ppiankov]

it does not crash if no index pre-exist and it creates a new one. it crashes only when there is an existing index.
Also even when it creates the index from scratch the index does not work as intended.

[evertsd]

Thanks for reporting @ppiankov, the issue has been identified and we're planning to fix in the next release. INTMDB-341 internal engineering ticket.

[Zuhairahmed]

@ppiankov brief update, we have allocated this fix to our next v1.8.0 release which should be out next week. will keep you posted when it has been released.

[Zuhairahmed]

@ppiankov we just released v1.8.0, feel free to give it try! issue should have been resolved.

[github-actions]

This issue has gone 30 days without any activity and meets the project’s definition of "stale". This will be auto-closed if there is no new activity over the next 30 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!