You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+61-1Lines changed: 61 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,14 @@ pterrafile [path]
20
20
21
21
If `path` is provided, it must be the path to a `Terrafile` file, or a directory containing one. If not provided, it looks for the file in the current working directory.
if --optimizedownloads is set to True then this indicates the usage of an opinionated Terrafile. The module names are used as the key in the terrafile and pterrafile will auto-detect the module names within your terrafiles and download only the matching names in your Terrafile. This allows you to utilize a single Terrafile at the top level of an environment. This is useful when you want to easily track the versions of all your modules in a single Terrafile and allows you to call out to this central Terrafile from sub folders, and only download the specific modules you require for terraform apply.
You run the pterrafile command from /dev/apps/ folder and example.git repo would be cloned into current working directory relative path modules/example thus ending up in dev/apps/modules/example
86
+
```
87
+
88
+
#main.tf located in apps
89
+
module "example" {
90
+
source = "modules/example/subfolder1"
91
+
}
92
+
93
+
#Terrafile located in DEV
94
+
example:
95
+
source: "https://github.com/joeblogs/example.git"
96
+
version: "master"
97
+
```
98
+
99
+
## Local installation, useful for Testing (python 3)
0 commit comments