Merge pull request #821 from imjaroiswebdev/response-play-eol-heads-up

[CSGI-2748] Response play documentation EOL heads up
PagerDuty · Feb 16, 2024 · 9e1b740 · 9e1b740
2 parents e09b16d + 8168170
commit 9e1b740
Show file tree

Hide file tree

Showing 5 changed files with 19 additions and 4 deletions.
diff --git a/website/docs/d/ruleset.html.markdown b/website/docs/d/ruleset.html.markdown
@@ -20,7 +20,7 @@ Use this data source to get information about a specific [ruleset][1] that you c
       target="_blank"
       >migrate to Event Orchestration</a>
     as soon as possible so you can take advantage of the new functionality, such
-    as improved UI, rule creation, APIs and Terraform support, advanced
+    as improved UI, rule creation, REST APIs and Terraform support, advanced
     conditions, and rule nesting.
   </p>
 </div>

diff --git a/website/docs/r/response_play.html.markdown b/website/docs/r/response_play.html.markdown
@@ -10,6 +10,21 @@ description: |-
 
 A [response play](https://developer.pagerduty.com/api-reference/b3A6Mjc0ODE2Ng-create-a-response-play) allows you to create packages of Incident Actions that can be applied during an Incident's life cycle.
 
+<div role="alert" class="alert alert-warning">
+  <div class="alert-title"><i class="fa fa-warning"></i>End-of-Life</div>
+  <p>
+    Response Play will end-of-life soon. We highly recommend that you
+    <a
+      href="https://support.pagerduty.com/docs/upgrade-response-plays-to-incident-workflows"
+      rel="noopener noreferrer"
+      target="_blank"
+      >migrate to Incident Workflows</a>
+    as soon as possible so you can take advantage of the new functionality.
+    With Incident Workflows, customers are able to define if-this-then-that
+    logic to effortlessly trigger a sequence of common incident actions, advanced conditions, REST APIs
+    and Terraform support.
+  </p>
+</div>
 
 ## Example Usage
 

diff --git a/website/docs/r/ruleset.html.markdown b/website/docs/r/ruleset.html.markdown
@@ -20,7 +20,7 @@ description: |-
       target="_blank"
       >migrate to Event Orchestration</a>
     as soon as possible so you can take advantage of the new functionality, such
-    as improved UI, rule creation, APIs and Terraform support, advanced
+    as improved UI, rule creation, REST APIs and Terraform support, advanced
     conditions, and rule nesting.
   </p>
 </div>

diff --git a/website/docs/r/ruleset_rule.html.markdown b/website/docs/r/ruleset_rule.html.markdown
@@ -20,7 +20,7 @@ An [event rule](https://support.pagerduty.com/docs/rulesets#section-create-event
       target="_blank"
       >migrate to Event Orchestration</a>
     as soon as possible so you can take advantage of the new functionality, such
-    as improved UI, rule creation, APIs and Terraform support, advanced
+    as improved UI, rule creation, REST APIs and Terraform support, advanced
     conditions, and rule nesting.
   </p>
 </div>

diff --git a/website/docs/r/service_event_rule.html.markdown b/website/docs/r/service_event_rule.html.markdown
@@ -20,7 +20,7 @@ A [service event rule](https://support.pagerduty.com/docs/rulesets#service-event
       target="_blank"
       >migrate to Event Orchestration</a>
     as soon as possible so you can take advantage of the new functionality, such
-    as improved UI, rule creation, APIs and Terraform support, advanced
+    as improved UI, rule creation, REST APIs and Terraform support, advanced
     conditions, and rule nesting.
   </p>
 </div>