From 54ff63a25dfdb80ba0e3f428efea78a67053bf69 Mon Sep 17 00:00:00 2001 From: Joey Orlando Date: Wed, 18 Dec 2024 17:27:36 -0500 Subject: [PATCH] chore: update pagerduty migrator docs --- tools/migrators/README.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/tools/migrators/README.md b/tools/migrators/README.md index d5f2810c6..841f80eb1 100644 --- a/tools/migrators/README.md +++ b/tools/migrators/README.md @@ -155,7 +155,14 @@ webhook integrations to adjust them for incoming payloads. This scenario may be relevant where you are unable to import your list of Grafana users, but would like to experiment with Grafana OnCall, using your existing PagerDuty setup as a starting point for experimentation. -If this is relevant to you, you can migrate as such: +If this is relevant to you, you can migrate as such 👇 + +> [!IMPORTANT] +> As outlined several times in the documentation below, if you first import data into Grafana OnCall without +> including users, make changes to that data within OnCall, and then later re-import the data with users, Grafana OnCall +> will delete and recreate those objects, as part of the subsequent migration. +> +> As a result, any modifications you made after the initial import will be lost. ```bash # Step 1: run a plan of what will be migrated, ignoring users for now