Skip to content

Commit

Permalink
chore: update pagerduty migrator docs
Browse files Browse the repository at this point in the history
  • Loading branch information
joeyorlando committed Dec 18, 2024
1 parent 62c4e86 commit 54ff63a
Showing 1 changed file with 8 additions and 1 deletion.
9 changes: 8 additions & 1 deletion tools/migrators/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 54ff63a

Please sign in to comment.