OPS-6704-mongodb-template-workaround

[YannickEvers]

Description

Workaround for a problem with the ionoscloud_mongo_template DataSource:
The id is null in the inital plan, but has the correct value when read later, resulting in a inconsistent final plan.

Error: Provider produced inconsistent final plan
When expanding the plan for
module.ionos_mongodb_cluster["cd"].ionoscloud_mongo_cluster.mongo_cluster to
include new values learned so far during apply, provider
"registry.terraform.io/ionos-cloud/ionoscloud" produced an invalid new value
for .template_id: was null, but now
cty.StringVal("6b78ea06-ee0e-4689-998c-fc9c46e781f6").
This is a bug in the provider, which should be reported in the provider's own
issue tracker.

The null_data_source resource "hides" the initial null, resulting in a consistent final plan.

  # module.ionos_mongodb_cluster["cd"].data.null_data_source.template_workaround will be read during apply
  # (depends on a resource or a module with changes pending)
 <= data "null_data_source" "template_workaround" {
      + has_computed_default = (known after apply)
      + id                   = (known after apply)
      + inputs               = {
          + "mongo_template_id" = null
        }
      + outputs              = (known after apply)
      + random               = (known after apply)
    }

Links to Tickets or other PRs

Notes

Approval for review

• All points were discussed with the ticket creator, support-team or product owner. The code upholds all quality guidelines from the PR-template.

Notice: Please remove the WIP label if the PR is ready to review, otherwise nobody will review it.