oncall-engine/tools/migrators/pytest.ini

[pytest]
env =
    D:PAGERDUTY_API_TOKEN=test
    D:ONCALL_API_TOKEN=test
    D:ONCALL_API_URL=test
    D:MIGRATING_FROM=pagerduty
    D:SPLUNK_API_ID=abcd
    D:SPLUNK_API_KEY=abcd
    D:OPSGENIE_API_KEY=abcd
    D:OPSGENIE_API_URL=test
Add PagerDuty migrator 2022-06-14 19:26:32 +03:00			`[pytest]`
			`env =`
			`D:PAGERDUTY_API_TOKEN=test`
			`D:ONCALL_API_TOKEN=test`
			`D:ONCALL_API_URL=test`
Splunk OnCall migration tool (#4267) # What this PR does Refactors the PagerDuty migration script to be a bit more generic + adds a migration script to migrate from Splunk OnCall (VictorOps) tldr; ```bash ❯ docker build -t oncall-migrator . [+] Building 0.4s (10/10) FINISHED ❯ docker run --rm \ -e MIGRATING_FROM="pagerduty" \ -e MODE="plan" \ -e ONCALL_API_URL="http://localhost:8080" \ -e ONCALL_API_TOKEN="<ONCALL_API_TOKEN>" \ -e PAGERDUTY_API_TOKEN="<PAGERDUTY_API_TOKEN>" \ oncall-migrator running pagerduty migration script... ❯ docker run --rm \ -e MIGRATING_FROM="splunk" \ -e MODE="plan" \ -e ONCALL_API_URL="http://localhost:8080" \ -e ONCALL_API_TOKEN="<ONCALL_API_TOKEN>" \ -e SPLUNK_API_ID="<SPLUNK_API_ID>" \ -e SPLUNK_API_KEY="<SPLUNK_API_KEY>" \ oncall-migrator migrating from splunk oncall... ``` https://www.loom.com/share/a855062d436a4ef79f030e22528d8c71 ## Checklist - [x] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will show up in the autogenerated release notes. 2024-05-14 09:53:59 -04:00			`D:MIGRATING_FROM=pagerduty`
			`D:SPLUNK_API_ID=abcd`
			`D:SPLUNK_API_KEY=abcd`
feat: add opsgenie to migrator script (#5495) This PR adds support for migrating data from OpsGenie to Grafana IRM. Closes https://github.com/grafana/irm/issues/1179 2025-04-07 08:47:27 -04:00			`D:OPSGENIE_API_KEY=abcd`
			`D:OPSGENIE_API_URL=test`