From e3fabd5e2ba2842cc9b2594b0693ed306d56a3a5 Mon Sep 17 00:00:00 2001 From: j-dunham Date: Mon, 15 Aug 2022 18:18:09 -0400 Subject: [PATCH] Update gitlab/valet-custom-transformers-lab.md Co-authored-by: Begona Guereca --- gitlab/valet-custom-transformers-lab.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/gitlab/valet-custom-transformers-lab.md b/gitlab/valet-custom-transformers-lab.md index e47dc1b..b9fc0aa 100644 --- a/gitlab/valet-custom-transformers-lab.md +++ b/gitlab/valet-custom-transformers-lab.md @@ -103,7 +103,9 @@ Also we can see the `PLAN_JSON` env has been updated to `custom_plan.json` + PLAN_JSON: 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. +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. + +Note: The custom transformers will only affect the pipeline being transformed if they contain the matching identifiers. If you believe a custom transformer should have altered the output, double check that the identifier is correct. ## Next Lab [Migrating a GitLab Pipeline](../gitlab/valet-migrate-lab.md)