From 91fbba23c16cf67a41b862ff225bd89b768cf3e8 Mon Sep 17 00:00:00 2001 From: pranav-new-relic Date: Wed, 16 Oct 2024 15:35:40 +0530 Subject: [PATCH] chore: final version of what the warnings should look like --- website/docs/r/synthetics_step_monitor.html.markdown | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/docs/r/synthetics_step_monitor.html.markdown b/website/docs/r/synthetics_step_monitor.html.markdown index 27fa5cd8e..b4456fc3d 100644 --- a/website/docs/r/synthetics_step_monitor.html.markdown +++ b/website/docs/r/synthetics_step_monitor.html.markdown @@ -10,7 +10,9 @@ description: |- Use this resource to create, update, and delete a Synthetics Step monitor in New Relic. --> **IMPORTANT:** The **Synthetics Legacy Runtime** reached end-of-life on October 22, 2024. Using the legacy runtime or blank runtime values with requests from the New Relic Terraform Provider will result in API errors. Starting with **v3.51.0** of the New Relic Terraform Provider, configurations without runtime attributes or comprising legacy runtime values will be deemed invalid. If your Synthetic monitors' configuration is not updated already with new runtime values, these consequences would be seen; upgrade as soon as possible to avoid consequences. For more details and instructions, please see detailed warning against `runtime_type` and `runtime_type_version` in the [**Argument Reference**](#runtime_type) section. +-> **IMPORTANT:** The **Synthetics Legacy Runtime** has reached its end-of-life on October 22, 2024. As a consequence, using the legacy runtime or blank runtime values with Synthetic monitor requests from the New Relic Terraform Provider will result in API errors. Starting with **v3.51.0** of the New Relic Terraform Provider, configurations of Synthetic monitors without runtime attributes or comprising legacy runtime values will be deemed invalid. +

+If your Synthetic monitors' configuration is not updated already with new runtime values, upgrade as soon as possible to avoid these consequences. For more details and instructions, please see the detailed warning against `runtime_type` and `runtime_type_version` in the [**Argument Reference**](#runtime_type) section. ## Example Usage