Open Pjack opened 4 weeks ago
We need to declare the value of each Terraform variable for every project, which makes the PR lengthy when adding new variables. Here are some examples. https://github.com/canonical/solutions-engineering-automation/pull/39/files https://github.com/canonical/solutions-engineering-automation/pull/69/files https://github.com/canonical/solutions-engineering-automation/pull/101/files
We should manage Terraform variables with a hierarchy, allowing us to define default values for the template. Reference doc: https://medium.com/@mehmetodabashi/terraform-variable-usage-the-order-of-precedence-for-variable-sources-c91586ddb13f
We can also consider to adopt terragrunt so that we can many the default value for each group. Ex: https://github.com/canonical/charm-engineering-repos/blob/main/teams/observability/repos/common.hcl
We need to declare the value of each Terraform variable for every project, which makes the PR lengthy when adding new variables. Here are some examples. https://github.com/canonical/solutions-engineering-automation/pull/39/files https://github.com/canonical/solutions-engineering-automation/pull/69/files https://github.com/canonical/solutions-engineering-automation/pull/101/files
We should manage Terraform variables with a hierarchy, allowing us to define default values for the template. Reference doc: https://medium.com/@mehmetodabashi/terraform-variable-usage-the-order-of-precedence-for-variable-sources-c91586ddb13f
We can also consider to adopt terragrunt so that we can many the default value for each group. Ex: https://github.com/canonical/charm-engineering-repos/blob/main/teams/observability/repos/common.hcl