This module uses the yamlencode and jsonencode Terraform functions to provide config contents from the variables supplied. There are two different outputs on this module, yaml and json. Either may be used to configure rke2. This is an "Independent" module, please see terraform.md for more information.
The specific use case for the example modules is temporary infrastructure for testing purposes.
With that in mind, it is not expected that we manage the resources as a team, therefore the state files are all stored locally.
If you would like to store the state files remotely, add a terraform backend file (*.name.tfbackend
) to your implementation module.
https://www.terraform.io/language/settings/backends/configuration#file
Please make sure to read terraform.md to understand the paradigms and expectations that this module has for development.
It is important to us that all collaborators have the ability to develop in similar environments, so we use tools which enable this as much as possible. These tools are not necessary, but they can make it much simpler to collaborate.
direnv allow
to enter the environmenttests
directory and run go test -v -timeout=5m -parallel=10
tests
directory and run go test -v -timeout=5m -run <test function name>
go test -v -timeout=5m -run TestBasic
override.tf
files to change the values of examples
to personalized data so that I can run themOur continuous integration tests in the GitHub ubuntu-latest runner, which has many different things installed.
When developing, we build variables.tf
based on the help command on the RKE2 binary.
This is a big topic, please see variables.md for more information.
You may want to test this code with slightly different parameters for your environment. Check out Terraform override files as a clean way to modify the inputs without accidentally committing any personalized code.