From f1637909f5e2f309aa9ac2d51150c6cdf1b59b0e Mon Sep 17 00:00:00 2001 From: j-dunham Date: Mon, 15 Aug 2022 15:54:14 -0400 Subject: [PATCH] Update valet-custom-transformers-lab.md --- gitlab/valet-custom-transformers-lab.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gitlab/valet-custom-transformers-lab.md b/gitlab/valet-custom-transformers-lab.md index ea05c18..c7a15b3 100644 --- a/gitlab/valet-custom-transformers-lab.md +++ b/gitlab/valet-custom-transformers-lab.md @@ -103,4 +103,4 @@ Also we can see the `PLAN_JSON` env has been updated to `custom_plan.json` Now that we have this custom transformers file we can add additional `transform`and `env` methods as needed and reuse it while running other `dry-run` and `migrate` commands. The custom transformers will only affect the pipeline being transformed if they contain the matching identifiers. This means if you think a custom transformer should have altered the output, then the first thing to check is if the identifier is correct. ## Next Lab -[Audit a GitLab Namespace](../gitlab/valet-audit-lab.md) +[Audit a GitLab Namespace](../gitlab/valet-migrate-lab.md)