-
terraform
Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
-
terragrunt-infrastructure-live-example
A repo used to show examples file/folder structures you can use with Terragrunt and Terraform
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
terraform-yaml-stack-config
Terraform module that loads an opinionated 'stack' configuration from local or remote YAML sources. It supports deep-merged variables, settings, ENV variables, backend config, and remote state outputs for Terraform and helmfile components.
-
terrafunk
Utility that allows you to execute terraform and terragrunt functions from the command line for quick tests and looking at underlying cty values
From my personal observation and experience, some drivers to Terragrunt seem to be related to outdated blog posts and this GitHub issue about not being able to use variables in the backend config.
I set up a project using the samples from terragrunt docs. Find them here: https://github.com/gruntwork-io/terragrunt-infrastructure-live-example and here: https://github.com/gruntwork-io/terragrunt-infrastructure-modules-example
Good point. What do you consider stacks? I have been following along with the CloudPosse world and the stack config i linked to, which does something similar but i think they are overkill for my environment.
Also, thanks for the link. Hadn't seen that solution before. Going to play around with that some when I have some time, it actually looks fairly similar to some of the stuff I do with my terragrunt templates. We use common yaml variables. And then I have some simple routines that do "deep merging" that allow you to have a huge level of granularity on how you can override them. Then more levels of overrides so you can hit individual resources inside of the stack. It's almost like a poor man's hiera to a degree. Then another helper utility called terrafunk that allows you to test this whole data layer super rapidly: TerrafunkAlways happy to take a look at other solutions I can borrow some ideas from. :)