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: CONTRIBUTING.md
+11-5Lines changed: 11 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,12 +19,17 @@ must be refreshed if the module interfaces are changed.
19
19
20
20
## Templating
21
21
22
-
To more cleanly handle cases where desired functionality would require complex duplication of Terraform resources (i.e. [PR 51](https://github.com/terraform-google-modules/terraform-google-kubernetes-engine/pull/51)), this repository is largely generated from the [`autogen`](/autogen) directory.
22
+
To more cleanly handle cases where desired functionality would require complex
this repository is largely generated from the [`autogen`](/autogen) directory.
23
26
24
-
The root module is generated by running `make build`. Changes to this repository should be made in the [`autogen`](/autogen) directory where appropriate.
27
+
The root module is generated by running `make build`. Changes to this
28
+
repository should be made in the [`autogen`](/autogen) directory where
29
+
appropriate.
25
30
26
-
Note: The correct sequence to update the repo using autogen functionality is to run
27
-
`make build`. This will create the various Terraform files, and then
31
+
Note: The correct sequence to update the repo using autogen functionality is to
32
+
run `make build`. This will create the various Terraform files, and then
28
33
generate the Terraform documentation using `terraform-docs`.
29
34
30
35
### Autogeneration of documentation from .tf files
@@ -56,7 +61,8 @@ Six test-kitchen instances are defined:
56
61
-`simple-zonal`
57
62
-`stub-domains`
58
63
59
-
The test-kitchen instances in `test/fixtures/` wrap identically-named examples in the `examples/` directory.`
64
+
The test-kitchen instances in `test/fixtures/` wrap identically-named examples
65
+
in the `examples/` directory.
60
66
61
67
### Test Environment
62
68
The easiest way to test the module is in an isolated test project. The
// auto upgrade by defaults only for regional cluster as long it has multiple masters versus zonal clusters have only have a single master so upgrades are more dangerous.
// auto upgrade by defaults only for regional cluster as long it has multiple masters versus zonal clusters have only have a single master so upgrades are more dangerous.
// auto upgrade by defaults only for regional cluster as long it has multiple masters versus zonal clusters have only have a single master so upgrades are more dangerous.
58
61
// When a release channel is used, node auto-upgrade are enabled and cannot be disabled.
0 commit comments