An easy to understand, opinionated terraform composable set of modules for CloudFlare, with batteries included 🔋.
These mono-repo contains a set of Terraform modules and recipes for provisioning CloudFlare resources. The modules are designed to be composable, and opinionated. The recipes are designed to be easy to understand, and easy to use.
Module | Description |
---|---|
✅Stable CloudFlare Zone | This module provide a way to create a CloudFlare zone with all the necessary configurations. |
The documentation is automatically generated by terraform-docs, and it's available in the module's README.md file.
- ⚡️Modules: refers to the actual module's directory. Where the
.tf
files reside. Eachsubdirectory
is a module. - ⚡️Examples: refers to the examples directory, where the examples recipes lives. These are also used for testing the infrastructure using Terratest. For its specific documentation, query this link
- ⚡️Tests: refers to the tests directory, where the tests recipes lives. These are also used for testing the infrastructure using Terratest. For its specific documentation, query this link
Some tools that this repo uses:
- 🧰 Terraform — strongly recommended the latest versions
- 🧰 Go — justified mostly for Terratest
- 🧰 TaskFile — for the automation of the tasks.
- 🧰 Make — for the automation of the tasks.
NOTE: For automation during the development process, I use precommit, which is a framework for managing and maintaining multi-language pre-commit hooks. It's a great tool, and I highly recommend it. All the hooks required are installed by this script. It's recommended though to run it through the TaskFile task
pre-commit-init
.
To initialize your pre-commit configuration, and ensure all the hooks are installed, run the following command:
# Using taskFiles
task pc-init
# Using make
make pc-init
To run these hooks against all the files, you can use the following Task
command:
# Using taskFiles
task pc-run
# Using make
make pc-run
This Module follows the principles of Semantic Versioning (SemVer).
Given a version number MAJOR.MINOR.PATCH
, we increment the:
MAJOR
version when we make incompatible changes,MINOR
version when we add functionality in a backwards compatible manner, andPATCH
version when we make backwards compatible bug fixes.
- Backwards compatibility in versions
0.0.z
is not guaranteed whenz
is increased. (Initial development) - Backwards compatibility in versions
0.y.z
is not guaranteed wheny
is increased. (Pre-release)
NOTE: The releases are automatically generated using release-please-action. For more information, please refer to the release-please-action documentation
Contributions are always encouraged and welcome! ❤️. For the process of accepting changes, please refer to the CONTRIBUTING.md file, and for a more detailed explanation, please refer to this guideline here.
This module is licensed under the Apache License Version 2.0, January 2004. Please see LICENSE for full details.
made/with ❤️ 🤟