From 667816eb1693fc18bfcaf2f41074cf954fbf22f8 Mon Sep 17 00:00:00 2001 From: Chris Trombley Date: Fri, 28 Jul 2023 10:09:34 -0700 Subject: [PATCH] docs: fix remaining problems from #405 (#406) --- website/docs/cloud-docs/workspaces/health.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/docs/cloud-docs/workspaces/health.mdx b/website/docs/cloud-docs/workspaces/health.mdx index 2ec4bba0e..fdbe5e398 100644 --- a/website/docs/cloud-docs/workspaces/health.mdx +++ b/website/docs/cloud-docs/workspaces/health.mdx @@ -113,8 +113,6 @@ Continuous validation regularly verifies whether your configuration’s custom a Continuous validation evaluates preconditions, postconditions, and check blocks as part of an assessment, but we recommend using [check blocks](https://developer.hashicorp.com/terraform/language/checks) for post-apply monitoring. Use check blocks to create custom rules to validate your infrastructure's resources, data sources, and outputs. -Continuous validation alerts you whenever an assertion fails, so you can change your configuration and avoid errors the next time you update infrastructure. - ### Preventing false positives Health assessments create a speculative plan to access the current state of your infrastructure. Terraform evaluates any check blocks in your configuration as the last step of creating the speculative plan. If your configuration relies on data sources and the values queried by a data source change between the time of your last run and the assessment, the speculative plan will include those changes. Terraform Cloud will not modify your infrastructure as part of an assessment, but it can use those updated values to evaluate checks. This may lead to false positive results for alerts since your infrastructure did not yet change.