Update gitlab/valet-custom-transformers-lab.md
Co-authored-by: Ethan Dennis <[email protected]>
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
# Using Custom Transformers in a `dry-run`
|
||||
In this lab we want to do a `dry-run` of the `terraform-example` project. Since we have already taken the `dry-run` lab we easily run the command and generate the GitHub workflow, but to our dismay Valet did not know how to transform the artifact report for Terraform and it shows as unsupported. After some research we determine that the action `actions/upload-artifact` would be an adequate substitute for it. This change will also require us to change the environment variable `PLAN_JSON` to point to a new value `custom_plan.json`. We need to make this change in many pipelines and an automated way to apply this would be ideal. Well, we are in luck we can use the `--custom-transformers` option of the `dry-run` command. This will allow us to change the behavior of Valet using a simple ruby file.
|
||||
In this lab we want to do a `dry-run` of the `terraform-example` project. We can now perform a `dry-run` of this project, however, we have discovered that the output will need to be customized to transform the Terraform artifact report. After some research, we have determined that the `actions/upload-artifact` action will be an adequate substitute for it. Additionally, we will need to change the environment variable `PLAN_JSON` to use to a different value: `custom_plan.json`. This customization will be present in many pipelines and an automated way to apply this would be ideal. In this lab, we will use the `--custom-transformers` option to change the behavior of Valet using its DSL built on top of the Ruby language.
|
||||
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [Write Custom Transformers](#write-custom-transformers)
|
||||
|
||||
Reference in New Issue
Block a user