Terraform apply failed with Error: Provider produced inconsistent final plan This is a bug in the provider, which should be reported in the provider's own issue tracker.

[devopsvj]

Terraform CLI and Terraform MongoDB Atlas Provider Version

Terraform v1.3.3
on windows_amd64

Terraform Configuration File

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

also tried with previous version of provider 1.4.6 same results 

Steps to Reproduce

Expected Behavior

Actual Behavior

Error: Provider produced inconsistent final plan

When expanding the plan for
module.mongo_base.module.mongodbatlas.mongodbatlas_x509_authentication_database_user.my_user
to include new values learned so far during apply, provider
"registry.terraform.io/mongodb/mongodbatlas" produced an invalid new value
for .certificates[0].id: was cty.NumberIntVal(6.656703865428611756e+18), but
now cty.NumberIntVal(6.656703865428612e+18).

This is a bug in the provider, which should be reported in the provider's own issue tracker.

Debug Output

Crash Output

Additional Context

The above issue is not happening with terraform cli 1.0.5 with mongo provider version 1.5.0

References

[Zuhairahmed]

hi @devopsvj, can you share config and log files with us so we can try to reproduce the error from our end?

also can you explain more what you mean by "The above issue is not happening with terraform cli 1.0.5 with mongo provider version 1.5.0"? The Terraform MongoDB Atlas Provider v1.5.0 is just the reference to the provider being used in the .tf files to create MongoDB Atlas resources.

[devopsvj]

@Zuhairahmed I mean to say, reported issue is not occurring when using terraform cli version 1.0.5 with mongo provider version 1.5.0.

1. Initial deployment using the terraform cli 1.3.3 successfully deployed resources.
2. However the issue is occurred when we tried to apply second time with with change in audit attributes.
3. On the same scenario, if we use terraform cli 1.0.5, reported issue is not occurring.

[Zuhairahmed]

ok thanks for more context, can you share your terraform config files so we can re-create issue from our end?

[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!