From 50b32d49a90109b2c4ed0bf18513d115720958cd Mon Sep 17 00:00:00 2001 From: Mike Bell Date: Mon, 10 Jun 2024 14:53:06 +0100 Subject: [PATCH] docs: update how to get resources --- runbooks/source/move-components-module.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/runbooks/source/move-components-module.html.md.erb b/runbooks/source/move-components-module.html.md.erb index 77be7265..a0a2d8e0 100644 --- a/runbooks/source/move-components-module.html.md.erb +++ b/runbooks/source/move-components-module.html.md.erb @@ -11,7 +11,7 @@ In order to migrate a terraform module from `components` into `core` there are a The aim is to make sure that when a terraform plan is run against both `core` and `compoents` after the MTM tool is ran there should be no terraform changes. -There is a pipeline in Concourse that accepts `$CLUSTER_NAME`, `$MODULE_NAME` and `$RESOURCE` setting these and running the pipeline will migrate that module/resource on the cluster specified. Resources can be passed as a comma seperated string. +There is a pipeline in Concourse that accepts `$CLUSTER_NAME`, `$MODULE_NAME` and `$RESOURCE` setting these and running the pipeline will migrate that module/resource on the cluster specified. Resources can be passed as a comma seperated string. Getting a list of resources to migrate is a manual process that requires you to read through the terraform files in `components`, some can be found by tracing back dependencies others should be obvious via there name. If you need to upgrade the `mtm` cli you can update the `$MTM_VERSION` parameter in the pipeline.