terraform/website
Quentin Machu f721608e4e provider/template: Add a 'dir' resource to template entire directories
When TerraForm is used to configure and deploy infrastructure
applications that require dozens templated files, such as Kubernetes, it
becomes extremely burdensome to template them individually: each of them
requires a data source block as well as an upload/export (file
provisioner, AWS S3, ...).

Instead, this commit introduces a mean to template an entire folder of
files (recursively), that can then be treated as a whole by any provider
or provisioner that support directory inputs (such as the
file provisioner, the archive provider, ...).

This does not intend to make TerraForm a full-fledged templating system
as the templating grammar and capabilities are left unchanged. This only
aims at improving the user-experience of the existing templating
provider by significantly reducing the overhead when several files are
to be generated - without forcing the users to rely on external tools
when these templates stay simple and that their generation in TerraForm
is justified.
2017-04-25 10:48:26 -07:00
..
scripts Re-enable soft purging, stale-if-error 2017-03-01 12:38:09 -05:00
source provider/template: Add a 'dir' resource to template entire directories 2017-04-25 10:48:26 -07:00
Gemfile Update basic scaffolding 2017-04-06 14:08:37 -04:00
Gemfile.lock Update basic scaffolding 2017-04-06 14:08:37 -04:00
LICENSE.md Update license 2017-03-08 11:38:20 -08:00
Makefile Update basic scaffolding 2017-04-06 14:08:37 -04:00
README.md Update middleman-hashicorp 2017-03-08 11:27:47 -08:00
config.rb v0.9.3 2017-04-12 20:21:42 +00:00
packer.json Update basic scaffolding 2017-04-06 14:08:37 -04:00

README.md

Terraform Website

This subdirectory contains the entire source for the Terraform Website. This is a Middleman project, which builds a static site from these source files.

Contributions Welcome!

If you find a typo or you feel like you can improve the HTML, CSS, or JavaScript, we welcome contributions. Feel free to open issues or pull requests like any normal GitHub project, and we'll merge it in.

Running the Site Locally

Running the site locally is simple. Clone this repo and run make website.

Then open up http://localhost:4567. Note that some URLs you may need to append ".html" to make them work (in the navigation).