-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
doc: uninstalling orchestrion (#505)
Signed-off-by: Eliott Bouhana <eliott.bouhana@datadoghq.com>
- Loading branch information
1 parent
e64a9d5
commit e835fa1
Showing
1 changed file
with
22 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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 | ||
|
||
{{<callout type="info">}} | ||
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`. | ||
{{</callout>}} |