From e7b3e2edb32dc3f176d3ea84f1057d4014e77901 Mon Sep 17 00:00:00 2001 From: j-dunham Date: Fri, 12 Aug 2022 15:33:59 -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 03365b9..5861700 100644 --- a/gitlab/valet-custom-transformers-lab.md +++ b/gitlab/valet-custom-transformers-lab.md @@ -50,7 +50,7 @@ jobs: with: path: VALUE_FROM_GITLAB ``` -- Now we know the final yaml we need we can write the ruby file. In this file we will call the `transform` method. This is a special method that Valet exposes, that takes the identifier we determined earlier and returns a Hash, which is basically the JSON version of the yaml we want. Valet will call that method when it encounters the identifer and pass in an `item`. The `item` is the values defined for that step in GitLab. In this case the path of the terraform report. +- Now we know the final yaml we can write the ruby file. In this file we will call the `transform` method. This is a special method that Valet exposes, that takes the identifier we determined earlier and returns a Hash, which is basically the JSON version of the yaml we want. Valet will call that method when it encounters the identifer and pass in an `item`. The `item` is the values defined for that step in GitLab. In this case the path of the terraform report. ```ruby transform "artifacts.terraform" do |item| {