From e835fa11b74a0594c6970b1d5b3d50d1a7f754bf Mon Sep 17 00:00:00 2001 From: Eliott Bouhana <47679741+eliottness@users.noreply.github.com> Date: Thu, 23 Jan 2025 13:18:55 +0000 Subject: [PATCH] doc: uninstalling orchestrion (#505) Signed-off-by: Eliott Bouhana --- _docs/content/docs/uninstalling.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 _docs/content/docs/uninstalling.md diff --git a/_docs/content/docs/uninstalling.md b/_docs/content/docs/uninstalling.md new file mode 100644 index 000000000..aa45ce49c --- /dev/null +++ b/_docs/content/docs/uninstalling.md @@ -0,0 +1,22 @@ +--- +title: "Uninstall" +weight: 999 + +prev: /troubleshooting +--- + +## Removing Orchestrion + +Removing Orchestrion from your project is a simple process to go back to the original state of your project before you +started using Orchestrion. + +The steps can be summed up as: +* Remove any files created by orchestrion like `orchestrion.tool.go` and `orchestrion.yml`. +* Run `go mod tidy` to remove any references to orchestrion in your `go.mod` file. +* Remove directives from your source code if any like `//orchestrion:ignore` or `//dd:span` +* Remove any references to orchestrion in your build scripts or CI/CD pipelines or Dockerfile + +{{}} +You can confirm that orchestrion has been removed correctly by looking at your application logs and checking +if they still contain the DataDog Tracer startup log starting with `DATADOG TRACER CONFIGURATION`. +{{}}