Comments on: Import configuration from Hiera or a Git repository with YAML files into Terraform https://jmorano.moretrix.com/2022/04/import-configuration-from-hiera-or-a-git-repository-with-yaml-files-into-terraform/ Ramblings of an old-fashioned space cowboy Sun, 15 Jan 2023 10:04:24 +0000 hourly 1 https://wordpress.org/?v=6.6.2 By: raff https://jmorano.moretrix.com/2022/04/import-configuration-from-hiera-or-a-git-repository-with-yaml-files-into-terraform/#comment-259286 Sun, 15 Jan 2023 10:04:24 +0000 https://jmorano.moretrix.com/?p=1393#comment-259286 Hey, have your right about using the terraform hiera provider? It adds his as a data source and can perform proper interpolation using hiera (ie: using the hierarch you have defined in your hiera.yaml). This means that it can perform lookups on a key with context. For example, I have my hierarchy:

– common/*
– environment/%{env}.yaml
– region/%{region}.yaml

So I can define my values at the most appropriate level, and have default values in common overridden by more specific values in environment or region.

To make this work, I typically encode his provider config (ie, the env & region) into the workspace name. So a single codebase can be used to deploy into multiple regions and environments. All your have to do it’s `terraform workspace new prod.us-east-1`, and run plan + apply. Your tf code needs to use a local to parse `${terraform workspace}` into env and region before passing them to the hiera provider.

]]>