Closed Kikivsantos closed 11 months ago
Thanks for opening this issue. The ticket INTMDB-1131 was created for internal tracking.
Hi @Kikivsantos, similarly to https://github.com/mongodb/terraform-provider-mongodbatlas/issues/1473 we cannot directly provide assistance on terraform+terragrunt integration.
In order for us to promptly help, we'll need you to be able to replicate the issue with by using our provider directly.
Said that, when you say But this configuretion does not use matcher.
what do you mean precisely? I see in your main.tf
file you are using the matcher
attribute: have you made sure you are passing the expected values?
Hi @marcosuma this is similar to the problem you guys resolved in the issue:
I'm creating a module to be used for our alerts. So I need to put all the possible options. That's why I use the "try()" on all the options that are not required for any alerts.
When I call this module that I created (my main.tf) I pass the values that I'm really going to use. It has to ingore all the rest - that's why we use try(..., null)
But the issue is just as the one you guys resolved on the one I opened before
Thanks
Ok, then if all good I am going ahead to resolve this one. Thank you @Kikivsantos
Hi, there.
I'm trying to create some alerts on mongoDB using terraform + terragrunt. It was working just fine, at least, until tuesday.
The error is on the plan. Saying that the matcher cannot be null. But this configuretion does not use matcher.
Terraform CLI and Terraform MongoDB Atlas Provider Version
Terraform Configuration File
My terraform code:
main.tf:
variable.tf
My terragrunt code:
1) For CPS_OPLOG_BEHIND
2) For CPS_SNAPSHOT_BEHIND
3) For CONNECTIONS_PERCENT:
Steps to Reproduce
terraform init
terraform plan
Expected Behavior
It should show the 3 alerts that would be created
Actual Behavior
Got the error below:
Debug Output
Crash Output
Additional Context
References